Analysis of HTTP 405 Error: Servlet Mapping Configuration and HTTP Method Handling Mechanism

Problem Phenomenon and Error Analysis

In Java Web development, beginners often encounter HTTP Status 405 errors, specifically "HTTP method GET is not supported by this URL." This error typically occurs due to improper Servlet configuration. The following analysis uses a user registration system case study.

The user provided complete registration system code, including a register.html form page, Register.java Servlet class, and web.xml configuration file. The form uses the POST method to submit data to the "Register" path:

<form action="Register" method="post">
    <!-- Form fields -->
</form>

The Servlet class implements only the doPost() method to handle POST requests:

public class Register extends HttpServlet{
    public void doPost(HttpServletRequest request, HttpServletResponse response){
        // Handle registration logic
    }
}

The issue lies in the web.xml configuration:

<servlet-mapping>
    <servlet-name>Register</servlet-name>
    <url-pattern>/register.html</url-pattern>
</servlet-mapping>

Deep Analysis of Error Mechanism

HTTP 405 error indicates "Method Not Allowed," meaning the requested HTTP method is not supported by the target resource. In this case, the fundamental cause is the mismatch between Servlet mapping configuration and HTTP method handling mechanisms.

First, the Servlet lifecycle is managed by the Web container. When a request arrives, the container finds the corresponding Servlet based on the url-pattern. Since the configuration maps the Servlet to /register.html, when users access this URL, the container does not return the HTML file but invokes the Register Servlet.

Second, the HttpServlet class implements the service() method by default, which calls appropriate methods like doGet() or doPost() based on request type. When a Servlet implements only doPost(), GET requests are rejected by the service() method, returning a 405 error.

The specific workflow is as follows:

1. User accesses http://localhost:8080/register.html
2. Web container finds Register Servlet based on url-pattern
3. Container calls Servlet's service() method
4. service() detects GET request, but Servlet implements only doPost()
5. Container returns HTTP 405 error response

Comparative Analysis of Solutions

Two main solutions exist for this problem, each with advantages and disadvantages.

Solution 1: Correct Servlet Mapping Path (Recommended)

This is the most RESTful design solution. Map the Servlet to an independent path to avoid conflicts with static resources:

<servlet-mapping>
    <servlet-name>Register</servlet-name>
    <url-pattern>/Register</url-pattern>
</servlet-mapping>

Also modify the HTML form's action attribute:

<form action="Register" method="post">

Advantages of this approach include:

• Complies with Servlet design standards, clear path structure
• Separation of static resources and dynamic processing
• Easy maintenance and extension
• Supports HTTP method semantics

Solution 2: Override Service Method

Override the service() method to forward all requests to doPost():

protected void service(HttpServletRequest request, HttpServletResponse response) 
        throws ServletException, IOException {
    doPost(request, response);
}

While this solves the problem, it has significant drawbacks:

• Violates HTTP method semantics, GET requests execute POST operations
• May create security vulnerabilities like CSRF attacks
• Not conducive to RESTful API design
• Poor code maintainability

Best Practices and Configuration Standards

Based on the analysis, the following best practices for Java Web development are proposed:

1. Servlet Mapping Standards: Servlets should be mapped to dedicated paths, avoiding conflicts with static resource paths. Use plural nouns like /users, /products.

2. HTTP Method Implementation: Implement appropriate HTTP methods based on business needs. Registration typically uses POST, queries use GET, updates use PUT, deletions use DELETE.

3. web.xml Configuration Optimization: Complete Servlet configuration should include initialization parameters, load order, etc.:

<servlet>
    <servlet-name>RegisterServlet</servlet-name>
    <servlet-class>com.example.Register</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>RegisterServlet</servlet-name>
    <url-pattern>/api/register</url-pattern>
</servlet-mapping>

4. Error Handling Mechanism: Implement doGet() method to provide user-friendly error pages, or use @WebServlet annotation to simplify configuration.

5. Security Considerations: Ensure sensitive operations are accessible only through appropriate HTTP methods, configure security constraints to prevent unauthorized access.

By following these best practices, developers can avoid common configuration errors and build more robust, maintainable Web applications.