syncliner.blogg.se

(2) By default, the response generated by a Servlet does depend on the HTTP method.

JSPs used as error pages must must ensure that they handle any error dispatch as a GET request, regardless of the actual method. There is a lot of security research being focussed on log4j2 at the moment and it is probable that additional information will emerge. The following represents the current understanding of the Apache Tomcat security team at the time this announcement was issued. Notes for other user provided error pages: (1) Unless explicitly coded otherwise, JSPs ignore the HTTP method. Mark Thomas - Tuesday, Decem1:51:56 AM PST. Each vulnerability is given a security impact rating by the. Depending on the original request this could lead to unexpected and undesirable results for static error pages including, if the DefaultServlet is configured to permit writes, the replacement or removal of the custom error page. This page lists all security vulnerabilities fixed in released versions of Apache Tomcat 7.x. If the error page is a static file, expected behaviour is to serve content of the file as if processing a GET request, regardless of the actual HTTP method.

This means that the request is presented to the error page with the original HTTP method. The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are forwarded to the error page.