AlliumPorrum wrote:
You were exactly right, headers look like this:
Server: Sun-Java-System/Application-Server
Date: Wed, 07 Nov 2007 17:44:10 GMT
Content-Type: text/html; ISO-8859-1;charset=ISO-8859-1
X-powered-by: Servlet/2.4
Transfer-Encoding: chunked
200 OK
So, the server really claims to use "chunked" messages. But the question now
is; how can I solve this problem in the HTTP client side, because the server
isn't made by me??
Simply use HTTP/1.0. A well-behaved HTTP/1.1 server will not use
chunk-coding when talking to a HTTP/1.0 client.
Hope this helps
Oleg
Roland Weber wrote:
Looks like the server claims to send a chunked message,
but then sends plain text without chunk information.
Check what value the Transfer-Encoding header of the
response has. If that says "chunked", but the server
doesn't chunk-encode the response, you'll get that kind
of exception.
hope that helps,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
