Hello Bastian, > Is there a little example how I can work with the > RequestEntity classes and a servlet.
You can't. RequestEntity in HttpClient 3.x is a client side interface which you can't use on the server side. HttpCore allows the use of RequestEntity on the server side, but it relies on HttpCore communication primitives which are different from the Servlet API. You might find something to clarify the usage of the interfaces in the test code for HttpClient 3.x and in the sample code for HttpCore 4.0 respectively. > I don't know how the data come from a servlet to > the HttpClient. It is sent over a TCP/IP or SSL connection. The same connection over which the request was sent to the server. > How will the server wrap the data and how can the > client unwrap it ? The server writes it's "wrapping" strategy in the Transport-Encoding header. The usual options are "id" (no header) and "chunked". HttpClient automatically interprets the Transport-Encoding header and decodes the chunked encoding if necessary. On the client side, you'll get the stream as it is sent by the server. Except if there is some proxy inbetween that applies a content encoding. If that is the case, the Content-Encoding header will tell you what encoding has been applied. hope that helps, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
