Transfer-Encoding: chunked In this case, it's most likely due to HTTP Chunked Transfer Encoding. It's normal.
...and you should process it differently based on the response header. Since the other side is apparently a Servlet, you can also just set the Content-Length header beforehand to avoid that it will send the body in chunks. You can use response.
SetContentLength() for that. – BalusC Jun 30 '10 at 1:28 Indeed, setting the content length is a good workaround. I'd also suggest using an existing HTTP client library (unless there are constraints against that).
There are plenty around and they tend to handle this well. – Bruno Jun 30 '10 at 1:31 Yes, I already commented that on the question :) – BalusC Jun 30 '10 at 1:32.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.