DO NOT REPLY [Bug 23181] New: - status 304 (Not modified) and chuncking leads to an wrong reponse

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23181>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23181

status 304 (Not modified) and chuncking leads to an wrong reponse

           Summary: status 304 (Not modified) and chuncking leads to an
                    wrong reponse
           Product: Apache httpd-2.0
           Version: HEAD
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: Hartmut.Keil@adnovum.ch


In the case of status 304 the 'Transfer-Encoding' encoding header will be 
supressed (http_protocol.c line 1672) but in 'chunk_filter(..)' the 
terminating chunk will be written in every case (http_core.c line 253).

So the following response results:

HTTP/1.1 304 Not Modified
Date: Thu, 11 Sep 2003 03:18:09 GMT
Server: Apache/2.0.45 (Unix) mod_ssl/2.0.45 OpenSSL/0.9.7b
Connection: close
ETag: excxgxgxuy6tre
Expires: Mon, 01 Jan 2004 01:00:00 GMT
0

And in the case of keep alive the client will read afer the next request 
the terminating chunk will  be readed first etc. 
And that is because the http spec. says explicitly in the case of 304 
ther is no body at all. (And that means not an empty body)

So chunking  ha sto be disabled for status 304 (http_protocol.c line 1672)

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org