Hello.
It looks like Tomcat 6.0.29 includes a version of Commons Daemon which
includes (wrongly I think) several .o and .a files.
I tried to compile jsvc by doing:
./configure
./make
And it failed with this message:
ar: libservice.a: Malformed archive
Then I realized that several object files
, Filip Hanik - Dev Lists devli...@hanik.comwrote:
The HTTP spec says that when you close the connection, that is the
delimiter for the content.
Filip
On 04/01/2010 04:02 AM, Óscar Frías Barranco wrote:
Hello.
Currently Tomcat HTTP 1.1 Connector disables the use of chunked encoding
...@hanik.comwrote:
so the spec says, use apples or oranges, we use oranges, and you want
apples
my suggestion would be to write a filter and set the chunked header
yourself
On 04/02/2010 09:25 AM, Óscar Frías Barranco wrote:
Ok, but it does not say that chunked encoding cannot be used when closing
Hello.
Currently Tomcat HTTP 1.1 Connector disables the use of chunked encoding if
keepalive is not used. This happens when an HTTP 1.1 request contains a
Connection: close header.
I propose to change Coyote to use chunked encoding (for HTTP 1.1) even if
keepalive is disabled.
Chunked
On Thu, Apr 1, 2010 at 12:52, Mark Thomas ma...@apache.org wrote:
So it comes down to Is the extra expense of chunked encoding a price
worth paying so UAs and proxies can tell if a response was unexpectedly
truncated, eg due to network error?
I don't have any hard figures (I'll see if I can
On Thu, Apr 1, 2010 at 12:39, Remy Maucherat r...@apache.org wrote:
His reverse proxy argument is probably the worst one: connection:
close does not land in the response by accident, it is added for good
reason. This is just begging for hacks at this point.
Sorry, I will try to clarify
