httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38070] - httpd returns status code 200 instead 304, but logged 304 in log.
Date Thu, 02 Feb 2006 20:06:08 GMT
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=38070>.
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=38070


Dave.Sparks@sisyphus.demon.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Dave.Sparks@sisyphus.demon.c
                   |                            |o.uk




------- Additional Comments From Dave.Sparks@sisyphus.demon.co.uk  2006-02-02 21:06 -------
Are you sure you don't want to convert a CGI-generated 200 to a 304 when the
HTTP conditions fail?  ap_scan_script_header_err is also called by mod_asis .  I
use mod_asis extensively, with files which include Last-Modified: and ETag:
headers, and it would be disastrous to return 200 when 304 would be appropriate.

Admittedly, I've had to patch both mod_asis.c and util_script.c to get the right
results, but my server seems to return the responses I expect.

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message