PrimeFaces FileUpload控件异常：ActionListener未触发且返回405状态码求助

Hey there, let's troubleshoot your PrimeFaces FileUpload issue where the ActionListener isn't firing and you're getting a 405 Method Not Allowed error. This is almost always a configuration misstep, so let's walk through each of your files and common pitfalls one by one.

First, understand the 405 error #

A 405 status means the server is rejecting the HTTP method your upload request is using. PrimeFaces FileUpload uses POST by default, so this usually points to either:

• Spring Security blocking POST requests to your upload endpoint
• Missing or misconfigured multipart request handling
• Incorrect servlet mapping or filter ordering

1. Check your web.xml for PrimeFaces FileUpload Filter #

The PrimeFaces FileUpload Filter must be configured correctly and mapped to your Faces Servlet, and it needs to run before any security filters (like Spring Security) so it can parse the multipart request first. Here's the correct setup:

<filter>
    <filter-name>PrimeFaces FileUpload Filter</filter-name>
    <filter-class>org.primefaces.webapp.filter.FileUploadFilter</filter-class>
    <!-- Optional threshold config for in-memory vs disk storage -->
    <init-param>
        <param-name>thresholdSize</param-name>
        <param-value>51200</param-value>
    </init-param>
</filter>
<filter-mapping>
    <filter-name>PrimeFaces FileUpload Filter</filter-name>
    <servlet-name>Faces Servlet</servlet-name>
</filter-mapping>

Double-check that:

• The filter class matches your PrimeFaces version (older versions might use org.primefaces.webapp.FileUploadFilter)
• The <servlet-name> exactly matches the name of your Faces Servlet in web.xml
• This filter comes before your Spring Security filter mapping in web.xml

2. Verify Spring Security Configuration #

Spring Security is a common culprit here. Let's fix two key things:

A. Allow multipart requests

Spring Security needs to know how to handle multipart/form-data requests. Add this bean to your Spring config:

@Bean
public MultipartResolver multipartResolver() {
    CommonsMultipartResolver resolver = new CommonsMultipartResolver();
    resolver.setMaxUploadSizePerFile(5242880); // 5MB example limit
    return resolver;
}

Or if you're using XML config:

<bean id="multipartResolver" class="org.springframework.web.multipart.commons.CommonsMultipartResolver">
    <property name="maxUploadSizePerFile" value="5242880"/>
</bean>

B. Ensure POST requests are permitted

Make sure your Spring Security config allows POST access to your JSF pages/upload endpoint. For example:

@Override
protected void configure(HttpSecurity http) throws Exception {
    http
        .authorizeRequests()
            .antMatchers("/your-upload-page.xhtml").permitAll() // Or apply appropriate roles
            .anyRequest().authenticated()
        .and()
        .csrf().disable(); // Temporarily disable CSRF to test (re-enable later!)
}

Note: PrimeFaces should automatically include the CSRF token in file upload requests, but disabling it temporarily can rule out CSRF as the issue.

3. Check pom.xml for Required Dependencies #

PrimeFaces FileUpload relies on Apache Commons libraries. Make sure these are present in your pom.xml:

<dependency>
    <groupId>commons-fileupload</groupId>
    <artifactId>commons-fileupload</artifactId>
    <version>1.4</version> <!-- Match with your PrimeFaces version (check PrimeFaces docs) -->
</dependency>
<dependency>
    <groupId>commons-io</groupId>
    <artifactId>commons-io</artifactId>
    <version>2.11.0</version>
</dependency>

Missing these will cause silent failures or multipart parsing errors that lead to 405s.

4. Validate Your JSF Page and Controller #

JSF Page Check

Ensure your p:fileUpload tag is correctly wired to your ActionListener, and uses the right mode:

<h:form>
    <p:fileUpload 
        fileUploadListener="#{uploadController.handleFileUpload}"
        mode="advanced"
        update="messages"
        allowTypes="/(\.|\/)(gif|jpe?g|png)$/"
        label="Select Files"/>
    <p:growl id="messages" showDetail="true"/>
</h:form>

• For mode="simple", you need to add enctype="multipart/form-data" to your <h:form> (advanced mode handles this automatically)
• The fileUploadListener EL expression must point to a valid managed bean method

Controller Method Check

Your ActionListener method must have the exact signature PrimeFaces expects:

import org.primefaces.event.FileUploadEvent;
import org.primefaces.model.UploadedFile;
import javax.faces.application.FacesMessage;
import javax.faces.context.FacesContext;
import javax.faces.view.ViewScoped;
import javax.inject.Named;

@Named
@ViewScoped
public class UploadController {

    public void handleFileUpload(FileUploadEvent event) {
        UploadedFile file = event.getFile();
        // Your file processing logic here
        FacesMessage msg = new FacesMessage("Success!", file.getFileName() + " was uploaded.");
        FacesContext.getCurrentInstance().addMessage(null, msg);
    }
}

Double-check:

• The bean is properly annotated (@Named/@ManagedBean with a valid scope like @ViewScoped)
• The method is public, returns void, and takes a FileUploadEvent parameter
• You're importing the correct PrimeFaces classes (not javax.servlet ones!)

5. Confirm Faces Servlet Mapping in web.xml #

Make sure your Faces Servlet is mapped correctly to handle your JSF pages. A common setup is:

<servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.xhtml</url-pattern>
</servlet-mapping>

If your mapping is something like /faces/*, ensure your page URLs include /faces/ (e.g., http://localhost:8080/your-app/faces/upload.xhtml). A mismatched mapping will send the request to the wrong servlet, causing a 405.

Quick Debugging Steps #

1. Temporarily disable Spring Security: If the upload works after disabling it, you know the issue is in your security config.
2. Inspect the browser request: Open your browser's dev tools (Network tab) and check:
   • Is the request method POST?
   • Is the Content-Type header multipart/form-data; boundary=...?
   • Is the request URL pointing to your JSF page (e.g., /upload.xhtml)?
3. Check server logs: Look for errors related to multipart parsing, Spring Security access denied, or Faces Servlet initialization.

内容的提问来源于stack exchange，提问作者Waqas Ahmed