> Well, after looking at the algorithm (and trying with a telnet), I think
the
> flag does the job. However, this is likely to be a capability which will
be
> going away when I rewrite the connector (since it adds complexity without
> adding anything useful - see below).
After the 'allowChunking=false' flag, I still got chunked responses. I can
make a simple test case if you would like that.
>
> Chunking is not optional for HTTP/1.1 compliance. If you support HTTP/1.1,
> you have to support chunked encoding (it's quite easy to do, actually, as
> it's a very simple encoding).
>
> Remy
The company I work for controls both the client and server. It is a
worldwide network for message delivery.
We have 3 web server constraints.
- Support for HTTP 1.1.
- Support for Keep-Alive.
- We do not want chunked encoding. Streamed responses will have the content
length in the header.
While HTTP 1.1 Compilance includes handling Cunked Encoding, it is not
necessary for a HTTP 1.1 response to be have chunked encoding. It is the
latter that I want.
The closest I have come to is replacing code in
<HttpResponseStream:checkChunking>
- useChunking = (!response.isCommitted()
- && response.getContentLength() == -1
- && response.getStatus() !=
- HttpServletResponse.SC_NOT_MODIFIED);
+ useChunking = false;
This causes problems with static resources and some other problems. I have a
feeling that this is really bad to do. Also I do not want to mentain such a
patch.
If the flag for 'allowChunking' is removed would it be possible to suggest
how one can cleanly add an extension to disable chunking. It is a must have
for us. Are there things in the Servlets that we can do to turn of chunking
? Can a servlet tell the Web Server , not to return data in chunks.
Is there a way to turn off chunking cleanly in the present. Any idiom/hint
etc. would be very appreciated.
thanks,
Harmeet
