Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.1.7
-
None
-
None
-
Operating System: other
Platform: Other
-
36872
Description
See http://marc.theaimsgroup.com/?t=112617026700001&r=1&w=2
And
http://marc.theaimsgroup.com/?t=111746450000002&r=1&w=2
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=109785174903101&w=2
When there are good reasons to block response headers set in internal pipelines,
we should at least output a warning to make it visible.
Also, it seems like 2.1.7 eats headers set by *mounted* sitemaps, which is not
correct, headers are needed for example to control front-end caches.
Need some test cases to verify this with mounted, internal and top-level
pipelines, and probably a fix for the "mounted" case.
And
http://marc.theaimsgroup.com/?t=111746450000002&r=1&w=2
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=109785174903101&w=2
When there are good reasons to block response headers set in internal pipelines,
we should at least output a warning to make it visible.
Also, it seems like 2.1.7 eats headers set by *mounted* sitemaps, which is not
correct, headers are needed for example to control front-end caches.
Need some test cases to verify this with mounted, internal and top-level
pipelines, and probably a fix for the "mounted" case.