> > 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
> 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=
> > You can use the HTTP/1.0 connector.
> >
> > Remy
>
> Unfortunatly I cannot. The application I have, requires HTTP 1.1 and
> Keep-Alive.
> HTTP 1.0 is not an option. However the client side libraries do not handle
> chunked encoding. So I am a bit stuck.
> Any help with turning off chunked enco
> You can use the HTTP/1.0 connector.
>
> Remy
Unfortunatly I cannot. The application I have, requires HTTP 1.1 and
Keep-Alive.
HTTP 1.0 is not an option. However the client side libraries do not handle
chunked encoding. So I am a bit stuck.
Any help with turning off chunked encoding with HTTP 1.
> Is there a way to completly disable chunking ?
> I have set allowChunking="false" in server.xml
>
> but may still turn chunking on for
> individual requests
>
> It has this code
> useChunking = (!response.isCommitted()
> && response.getContentLength() == -1
> && resp