tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3823] - sendError and setStatus clear headers already set
Date Tue, 25 Sep 2001 22:36:51 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=3823>.
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=3823

sendError and setStatus clear headers already set





------- Additional Comments From brett.knights@tanner.com  2001-09-25 15:36 -------
Overriding any already set headers can be done with the setHeader methods 
rather than addHeader methods.

The spec is pretty clear on what should happen and the reference implementation 
should comply with the spec so whether it's risky or not (or my proposed fix 
works or not) shouldn't really make any difference to whether this bug gets 
assigned a high priority or not.

FWIW I have a bunch of applications running using this and, while I may go to 
realm based security in the future, I don't want to have to change something 
thta isn't broken.

Mime
View raw message