You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Rainer Jung <ra...@kippdata.de> on 2008/02/19 10:32:07 UTC

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.

Or do you think, there's no related bug in the AJP connector? Then you 
might like toadd a comment.

Regards,

Rainer

bugzilla@apache.org wrote:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://issues.apache.org/bugzilla/show_bug.cgi?id=40317>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
> INSERTED IN THE BUG DATABASE.
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=40317
> 
> 
> william.barker@wilshire.com changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |tneidhart@know-center.at
> 
> 
> 
> 
> ------- Additional Comments From william.barker@wilshire.com  2008-02-18 17:29 -------
> *** Bug 44448 has been marked as a duplicate of this bug. ***

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


Re: DO NOT REPLY [Bug 40317] - mod_jk, mixed up response if request contains http status 304 - resources with Content-Length > 0

Posted by Jim Jagielski <ji...@jaguNET.com>.
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


RE: DO NOT REPLY [Bug 40317] - mod_jk, mixed up response if request contains http status 304 - resources with Content-Length > 0

Posted by Bill Barker <wb...@wilshire.com>.
 

> -----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.  

> Or do you think, there's no related bug in the AJP connector? 
> Then you 
> might like toadd a comment.
> 
> Regards,
> 
> Rainer
> 
> bugzilla@apache.org wrote:
> > DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG.
> > RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> > <http://issues.apache.org/bugzilla/show_bug.cgi?id=40317>.
> > ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND.
> > INSERTED IN THE BUG DATABASE.
> > 
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=40317
> > 
> > 
> > william.barker@wilshire.com changed:
> > 
> >            What    |Removed                     |Added
> > 
> --------------------------------------------------------------
> --------------
> >                  CC|                            
> |tneidhart@know-center.at
> > 
> > 
> > 
> > 
> > ------- Additional Comments From 
> william.barker@wilshire.com  2008-02-18 17:29 -------
> > *** Bug 44448 has been marked as a duplicate of this bug. ***
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
> 
> 
> 



This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.


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