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=39647>. 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=39647 ------- Additional Comments From [EMAIL PROTECTED] 2006-05-26 22:59 ------- Created an attachment (id=18358) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18358&action=view) Patch against mod_jk.c (1.3 Version) of mod_jk 1.2.15 Apart from the patch against 2.2.x I am pretty much sure that the behaviour of the backend (sending Content-Length and Content-Type for a 304 response) is not compliant with RFC 2616. 10.3.5 in RFC 2616 states: The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields. I read this as Content-Length and Content-Type header MUST NOT be sent with 304 responses and the behaviour of httpd 2.2.x and the http connector of Tomcat not doing this seem to support this view. >From my limited point of view on httpd 1.3 this should be fixed inside mod_jk. I think that the attached patch, which is untested due to my lack of an available httpd 1.3, does this without breaking other things. So, if you like you can give the attached patch a try to make your backend RFC 2616 compliant again :-). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
