In my case there is no stack trace. The browser is the client. Browser waits
for the data to come but I can clearly see that the page has transferred to
the browser. This means that the chunking is incorrect and browser thinks
there is more data to come.
When I force content length to the browser this worked confirming my
suspicion in chunked encoding.
Supun
I suggest you try it again with the updated ChunkedEncoder with a build
off trunk. Else, and SSL debug will show you the transfer in hex to
manually check if the encoding resulted in a fault
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
