You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2008/06/11 15:30:52 UTC
DO NOT REPLY [Bug 45026] Custom HTTP-Error codes get remapped to
500er codes
https://issues.apache.org/bugzilla/show_bug.cgi?id=45026
Jens Scheffler <je...@hp.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jens.scheffler@hp.com
--- Comment #8 from Jens Scheffler <je...@hp.com> 2008-06-11 06:30:51 PST ---
Thanks for the information - while 1.2.27 of the plugin is still not fully
released and also the httpd will take a moment to get this implemented we
managed to change our code to always include a reason phrase - the servlet spec
allows to send one or leave it out. If a correct reason is provided, it is
working out fine.
when the code...
response.setStatus(int) or
response.sendError(int)
...is used, the problem is showing up and HTTP 500 is returned to user.
If we use the both methods...
response.setStatus(int, String) or
response.sendError(int, String)
...and the String is NOT NULL, then the resulting HTTP response code is
correct.
Thanks & Best Regards,
Jens
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org