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=41179>. 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=41179 Summary: 400 Bad Request response during auto re-deployment Product: Tomcat 5 Version: 5.5.20 Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: P5 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When you re-deploy the root war file using autoDeploy="true", Tomcat sends a response with status code 400 (Bad Request: No host matches ...). This makes it impossible to serve a custom error document with Apache + mod_jk since the request processing is immediately halted to guard against security problems caused by bad requests. (See: http://httpd.apache.org/docs/2.0/mod/core.html#errordocument) RFC 2616 (section 10.4.1) says about status code 400: "The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications" The thing is, that there's nothing wrong with the client's request. It's not a syntactical issue and indeed the client SHOULD repeat the request. I wonder whether a 404, 500 or 503 wouldn't be more appropriate here, at least this would allow one to serve a custom error document during re-deployments. -- 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
