Tomcat4 + IIS5 + mod_jk2-2.0.4 : Problem on POST with Transfer-Encoding: chunked header

contains an XML document in the request body. Whenever I post a request thru IIS with a header Transfer-Encoding: chunked, the body of the request is missing (HttpServletRequest.getInputStream() is empty) and my program can not continue because the XML document is not there. This works fine if I

Tomcat-IIS-JK2 : Problem on POST with Transfer-Encoding: chunked

I have successfully configured JK2 to have IIS working with Tomcat. However, I am having a problem: My servlet receives a HTTP request from client which contains an XML document in the request body. Whenever I post a request thru IIS with a header Transfer-Encoding: chunked, the body

Data-Streaming : Transfer-Encoding: chunked

-Encoding: chunked Date: Fri, 14 Feb 2003 14:11:22 GMT Server: Apache Coyote/1.0 Connection: close -- Bjarne Jørgensen [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Transfer encoding chunked

Hi, recently I upgraded to Tomcat 4.1.10. I noticed that it is using transfer encoding chunked automagically for some content types (image/tiff, audio/x-wav and probably some more). Is there any way to avoid this behavior? Thanks in advance for any help, Clemens Viehl -- To unsubscribe, e

Re: Transfer encoding chunked

[EMAIL PROTECTED] wrote: Hi, recently I upgraded to Tomcat 4.1.10. I noticed that it is using transfer encoding chunked automagically for some content types (image/tiff, audio/x-wav and probably some more). Is there any way to avoid this behavior? You need to set the content-length

RE: Transfer encoding chunked

Hi, You need to set the content-length of the response before it is committed (or have the response fit in the 4K buffer). Thanks for the quick response! I'll check this! Bye Clemens -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL

RE: Transfer encoding chunked

Hi, You need to set the content-length of the response before it is committed (or have the response fit in the 4K buffer). you're of course right about the transfer encoding. Unfortunately that hasn't solved my original problem. I have found the solution now. I don't want to bore people

Transfer-Encoding: chunked

Jakarta STRUTS, but I think, that's not the point of matter. But what I found was the Transfer-Encoding: chunked header and some numbers grabled into the HTML. Here is the request and bad response (please note the 102f and 0). I think that is the problem. Now: 1. May that be really the problem

Re: Transfer-Encoding: chunked

also using Jakarta STRUTS, but I think, that's not the point of matter. But what I found was the Transfer-Encoding: chunked header and some numbers grabled into the HTML. Here is the request and bad response (please note the 102f and 0). I think that is the problem. Now: 1. May that be really

Re: Transfer-Encoding: chunked

, which does not open correctly in Netscape (can't view HTML source code) and causes IE to open some temporary file on the local file system (C://documents...). BTW: I'm also using Jakarta STRUTS, but I think, that's not the point of matter. But what I found was the Transfer-Encoding

tomcat 4.0b7: Transfer-Encoding: chunked

HttpInspector please find those below. The difference in the response from tomcat is that when excels asks for the page it will include the Transfer-Encoding: chunked header and some numbers grabled into the html. Here is the full bad response (please note the 299 and 0 which miss completly when the same