cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helma van der Linden (JIRA)" <>
Subject [jira] Closed: (COCOON-430) Wrong handling of HTTP Headers
Date Tue, 25 Oct 2005 13:44:03 GMT
     [ ]
Helma van der Linden closed COCOON-430:

    Resolution: Fixed

> Wrong handling of HTTP Headers
> ------------------------------
>          Key: COCOON-430
>          URL:
>      Project: Cocoon
>         Type: Bug
>   Components: * Cocoon Core
>     Versions: 2.0.5-dev (Current CVS)
>  Environment: Operating System: All
> Platform: All
>     Reporter: Carsten Ziegeler
>     Assignee: Cocoon Developers Team
>     Priority: Critical

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message