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=27432.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
27432] New: - Malformed HTTP
headers (debug information in Parameters object)
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=27432.
ANY REPLY MADE TO THIS MESSAGE
Le Jeudi, 4 mars 2004, à 14:37 Europe/Zurich, Carsten Ziegeler a écrit :
...I think, we should disable this feature for now and find a better
and compatible way
Wouldn't just changing the header name from
org.apache.cocoon.sitemap/Location to something like
X-Cocoon-debug-sitemap-location
Bertrand Delacretaz wrote:
Le Jeudi, 4 mars 2004, à 14:37 Europe/Zurich, Carsten
Ziegeler a écrit :
...I think, we should disable this feature for now and find
a better
and compatible way
Wouldn't just changing the header name from
org.apache.cocoon.sitemap/Location to
Bertrand Delacretaz wrote:
Le Jeudi, 4 mars 2004, à 15:01 Europe/Zurich, Carsten
Ziegeler a écrit :
Bertrand Delacretaz wrote:
...Using a known prefix like X-Cocoon-debug- also makes
it easy to
filter out these headers when needed.
But then you have to change every component
Le Jeudi, 4 mars 2004, à 15:07 Europe/Zurich, Carsten Ziegeler a écrit :
...Yes, so if someone knows where this is used/useful we can perhaps
think about an alternative.
It is used to add location info to Exceptions, for example in
o.a.c.matching.AbstractRegexpMatcher.preparedMatch()
(search for
Wouldn't just changing the header name from
org.apache.cocoon.sitemap/Location to something like
X-Cocoon-debug-sitemap-location fix the problem?
Perhaps in this special case, I don't know, perhaps Lars can answer this.
Just renaming might solve it, but I would not be happy with this
Bertrand Delacretaz wrote:
Le Jeudi, 4 mars 2004, à 15:07 Europe/Zurich, Carsten Ziegeler a écrit :
...Yes, so if someone knows where this is used/useful we can perhaps
think about an alternative.
It is used to add location info to Exceptions, for example in
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 04, 2004 1:21 PM
To: [EMAIL PROTECTED]
Subject: DO NOT REPLY [Bug 27432] New: - Malformed HTTP
headers (debug information in Parameters object)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED
Carsten Ziegeler wrote:
Bertrand Delacretaz wrote:
Le Jeudi, 4 mars 2004, à 14:37 Europe/Zurich, Carsten
Ziegeler a écrit :
...I think, we should disable this feature for now and find
a better
and compatible way
Wouldn't just changing the header name from
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Bertrand Delacretaz wrote:
Le Jeudi, 4 mars 2004, à 14:37 Europe/Zurich, Carsten Ziegeler a écrit :
...I think, we should disable this feature for now and find
a better
and compatible way
Wouldn't just changing the header
Unico Hommes wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
snip/
But then you have to change every component that currently iterates
over the parameters and every component has to filter.
We actually really introduced an incompatible feature and to be
honest, I don't even know where
Le Jeudi, 4 mars 2004, à 22:56 Europe/Zurich, Sylvain Wallez a écrit :
Although individual parameter location may be useful, the location
parameter I'm talking about is that of the statement. This makes me
think SitemapParameters with a getStatementLocation() is better
than
Sylvain Wallez wrote:
So here's a proposal (I should have thought about it way earlier...):
let's use a LocatedParameters, subclass of Parameters
with an additional getLocation() method. It has no impact
on components that iterate on parameters, and yet still
provide location whenever
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
So here's a proposal (I should have thought about it way
earlier...):
let's use a LocatedParameters, subclass of Parameters
with an additional getLocation() method. It has no impact on
components that iterate on parameters, and yet
15 matches
Mail list logo
