tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: DO NOT REPLY [Bug 40317] - mod_jk, mixed up response if request contains http status 304 - resources with Content-Length > 0
Date Thu, 21 Feb 2008 17:58:07 GMT

On Feb 19, 2008, at 1:35 PM, Bill Barker wrote:

>
>
>> -----Original Message-----
>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>> Sent: Tuesday, February 19, 2008 1:32 AM
>> To: Tomcat Developers List
>> Subject: Re: DO NOT REPLY [Bug 40317] - mod_jk, mixed up
>> response if request contains http status 304 - resources with
>> Content-Length > 0
>>
>> Hi Bill,
>>
>> why do we close this as duplicate?
>>
>> The other bug has been closed as "not a mod_jk bug", but in this case
>> the user gave evidence, that the might be something broken in
>> the TC AJP
>> connector. So shouldn't we keep this one open and only change
>> the component.
>>
>
> If it isn't mod_jk's job to sanitize the HTTP output, then it  
> certainly
> isn't the job of the AJP connector ;).  The AJP connector has no  
> reason to
> even know that httpd received the request via HTTP.
>
> It's possible that there is a bug with DefaultServlet that creates 304
> responses with a Content-Length, but I doubt it.
>
>>

Appears to me that the AJP connector is borked... Will look.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message