Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Subject: DO NOT REPLY [Bug 36872]  -
    Internal pipelines eat HTTP headers without warning
Message-Id: <20051010085724.4D09D243@ajax.apache.org>
Date: Mon, 10 Oct 2005 10:57:24 +0200 (CEST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36872>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36872


------- Additional Comments From bdelacretaz@codeconsult.ch  2005-10-10 10:57 -------
We've discussed this with Vadim and Carsten at the GT, and came to the
conclusion that in most cases eating headers is the right thing to do in
internal pipelines (but this should be logged, which is not the case now).

For the few cases (and there are valid ones indeed) where headers must be set
from internal pipelines, the cleanest seems to be a customized SitemapSource,
which would be configurable to allow some or all headers to go through. Or
inherit from SitemapSource and create a different EnvironmentWrapper. 

This could be configured with a different protocol name,
"cocoon-wheaders:/someURL" or something.

I'll probably implement this eventually, unless someone beats me to it. But at
we least we know exactly what's happening - and my initial report about this
happening for mounted sitemaps as well was wrong, sorry about the noise.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.