[
https://issues.apache.org/jira/browse/COCOON-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski updated COCOON-2009:
-----------------------------------------
Attachment: cocoon-pipeline-impl-http-compliant-patch-2.txt
cocoon-pipeline-impl-http-compliant-patch-2.txt:
I've changed Last-Modified header value calculation. Now it's the same as in
response that is cached.
NOTE: Someone could also wonder why there are so many places where HTTP OK is
set and why it could not be done in AbstractProcessingPipeline's proces()
method as it is seems to be the best place. Of course, it would be fantastic to
set it one place, but this method does not know if some component somewhere
deep in the processing tree has not set status code already (to 302 value).
Personally, I'm do not understand why components are allowed to manipulate
status code/response headers but I'll write my thoughts on the list someday.
> Pipelines more HTTP-compliant (respecting and producing HTTP headers and
> status codes)
> --------------------------------------------------------------------------------------
>
> Key: COCOON-2009
> URL: https://issues.apache.org/jira/browse/COCOON-2009
> Project: Cocoon
> Issue Type: Improvement
> Components: - Components: Sitemap
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Grzegorz Kossakowski
> Fix For: 2.2-dev (Current SVN)
>
> Attachments: cocoon-pipeline-impl-http-compliant-patch-1.txt,
> cocoon-pipeline-impl-http-compliant-patch-2.txt
>
>
> This issue was discussed a little here:
> http://news.gmane.org/find-root.php?group=gmane.text.xml.cocoon.devel&article=70383
> Main aim is to respect cache-related headers and produce necessary
> information for clients to do proper caching.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
