cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12915] New: - Wrong handling of HTTP Headers
Date Mon, 23 Sep 2002 10:14:31 GMT
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=12915>.
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=12915

Wrong handling of HTTP Headers

           Summary: Wrong handling of HTTP Headers
           Product: Cocoon 2
           Version: Current CVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: core
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: cziegeler@apache.org


HTTP Headers are not handled correctly for Readers:
When a binary content is queried the second time by the same client, the client 
usually sents the "If-Modified-Since" header. The HttpEnvironment compares this 
information with the last modification date of the source used for the reader.
If this date comparisson is successful, Cocoon immediately returns to the 
client and no new generation takes place - because the browser has the content 
cached.
This seems correct, but is actually dead wrong! This only works if the reader 
always reads the same src, but if the reader for example randomly chooses an 
image, the src does change but perhaps not the last modification date (if all 
srcs have the same last modification date for example - which is usual for 
deployed web applications).
So the client always displays the image of the first request.

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


Mime
View raw message