Summary: | 500 Internal Error and Content-Type not honored. | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Jules Damji <jules.damji> |
Component: | Connector:Coyote | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jules.damji, nick.atkins |
Priority: | P2 | ||
Version: | 5.0.28 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP |
Description
Jules Damji
2005-01-11 03:14:49 UTC
Please submit a ready to test WAR. We are encountering this bug also - we are using webMethods GLUE to generate SOAP packets. On Tomcat 4.x and Tomcat 5.0.x prior to 5.0.28 we have seen no problem. On 5.0.28 we are seeing our SOAP faults being sent with Content-Type: text/html, which is causing the client problems in handling the message. Since I didn't get a test case ... Are you using sendError to set the 500 ? I think I see a possible problem with the algorithm in the error report valve (which is also inefficient in that particular situation). I've committed code in the 5.5 CVS. Please test it if you can. The workaround, assuming I am right about the bug, is to commit the response (call flush on the reponse, for example). No. We use HttpServletResponse.setStatus (HttpServletResponse.SC_INTERNAL_ERROR). As for the war file, I am in the middle of release and a bit swamped, but it is fairly reproducible. But a small servlet deployed under TC 5.0.28 returning the above and then setting MimeHeaders to add content-type, content-length should do the job. This should be fixed in the Tomcat 5.5 CVS then. I'm taking Remy's word on faith. If you test 5.5.9 and find it's still broken, feel free to reopen with the new data and a test case we can (hopefully) reproduce. |