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 7952] New: - No 'Last-Modified' header in the HTTP response
Date Thu, 11 Apr 2002 10:26:20 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=7952>.
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=7952

No 'Last-Modified' header in the HTTP response

           Summary: No 'Last-Modified' header in the HTTP response
           Product: Cocoon 2
           Version: 2.0.3
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: anatoly@k2s.ru


Bug:

Cocoon (2.0.3-dev 2002-03-03) doesn't produce and return the Last-Modified 
header in the HTTP response.

The patch attached proposes the solution to this problem:
- it makes CachedObjects to store their birth timestamp in the cache (we 
cannot rely to TimestampValidity here)
- it extends Environment with the methods that set the timestamp for the 
response
- it alters CachingPipelines to set these stamps at appropriate times
- it alters CocoonServlet to allow Last-Modified header to make it's way 
through (I don't fully understand why it was needed, really :-)

Sorrily due to the problems with my Internet access I cannot reliably work 
with your CVS server 
and produce standard diff, so I've jarred all relevant sources files.

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


Mime
View raw message