[ https://issues.jboss.org/browse/JBWEB-301?page=com.atlassian.jira.plugin.... ] Aaron Ogburn commented on JBWEB-301: ------------------------------------ Let me note what happens specifically with DELETE/PUT and PATCH requests First, here's what occurs with DELETE/PUT requests: 1) filter sends 405 2) StandardHostValve tries to serve custom error page, forwarding to custom 405 page. 3) Static 405 error page is served by org.apache.catalina.servlets.DefaultServlet. It is still serving the original method for the forwarded error page request (DELETE or PUT). DefaultServlet provides 403 in its doPut/doDelete implementations. So the put/delete to the static page gets a 403 in the end from the custom error page. And now for PATCH requests: 1) filter sends 405 2) StandardHostValve tries to serve custom error page, forwarding to custom 405 page. 3) Static 405 error page is served by org.apache.catalina.servlets.DefaultServlet. It is still serving the original method for the forwarded error page request (PATCH). DefaultServlet extends javax.servlet.http.HttpServlet and does not override the HttpServlet.service method. HttpServlet.service does not recognize the PATCH request method, and so it provides a 501/method not implemented response. So in both cases, JBoss forwards the request to the custom error page, and the result of that forwarded request sets the end response code, overriding what your filter set. Note the following portion from the servlet spec (JSR 315, Section 10.9.1): ... If the location of the error handler is a servlet or a JSP page: * The original unwrapped request and response objects created by the container are passed to the servlet or JSP page. * The request path and attributes are set as if a RequestDispatcher.forward to the error resource had been performed. ... So we should expect the request to be forwarded to the error pages, which are handled by the DefaultServlet, and we should expect the end custom error page response from the DefaultServlet to override the filter's set 405. It looks like everything is working as intended here and there is no actual bug, although the end result is not your desired result. Your complaint would actually be against the servlet spec itself and not JBossWeb, which is just following the spec. -- This message was sent by Atlassian JIRA (v6.2.6#6264)