Re: Adding Content-Length response header

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 3/26/13 11:08 AM, Konstantin Kolinko wrote: > 2. Are you interested in GET/POST requests, or HEAD requests? > > HEAD requests were fixed by this commit, from 5 days ago > http://svn.apache.org/r1459087 I am dealing almost entirely

RE: Adding Content-Length response header

>-Original Message- >From: Christopher Schultz [mailto:ch...@christopherschultz.net] >Subject: Adding Content-Length response header > >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA256 > >All, > >Here's the situation I have: I've got a respo

Re: Adding Content-Length response header

On Mar 26, 2013, at 3:15 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Konstantin, > > On 3/26/13 11:08 AM, Konstantin Kolinko wrote: >> 2013/3/26 Christopher Schultz : >>> >>> Like most folks on the list, I have quite a few dynamic >>> resources being

Re: Adding Content-Length response header

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 3/26/13 11:08 AM, Konstantin Kolinko wrote: > 2013/3/26 Christopher Schultz : >> >> Like most folks on the list, I have quite a few dynamic >> resources being served through Tomcat. For nearly all of them, >> the Content-Length respo

Re: Adding Content-Length response header

2013/3/26 Christopher Schultz : > > Like most folks on the list, I have quite a few dynamic resources > being served through Tomcat. For nearly all of them, the > Content-Length response header is /not/ included in the response > because either content length isn't known when the response is > comm

Adding Content-Length response header

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, Like most folks on the list, I have quite a few dynamic resources being served through Tomcat. For nearly all of them, the Content-Length response header is /not/ included in the response because either content length isn't known when the respo