What are the general thoughts on the stability of the
enable_chunked_encoding option for the IIS isapi redirector for tomcat
and IIS?
We're running into a scenario where something is causing IIS to not send
down the complete response. Haven't figured out exactly the cause yet,
but the symptoms are the browser never acknowledges a response was
complete even though tomcat has fully written the response out through
to the web server. Wireshark captures show the last few packets not
being sent so the response is just a little short of what's to be expected.
One thing we noticed was setting enable_chunked_encoding (with a
redirectory built for chunked encoding of course) made everything work
fine so I wanted to get a feel for just how experimental this really is
and what the general consensus is on it's stability.
Thanks,
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org