Laravel中PUT/PATCH请求无法进入update方法，出现404错误求助

Hey Diego, let's work through this 404 issue with your HomeController's update method—this is a super common snag, so we'll get it fixed in no time. Here are the most likely culprits to check:

1. Verify Your Resource Route is Registered #

First, make sure you've actually registered the resource route in routes/web.php (or routes/api.php if it's an API endpoint):

// web.php
Route::resource('home', HomeController::class);

Run php artisan route:list to confirm the update route exists. You should see an entry like this:

PUT|PATCH | /home/{home} | home.update | App\Http\Controllers\HomeController@update

If this entry is missing, double-check your route registration—typos here are easy to miss!

2. Ensure Your Request Uses the Correct URL & HTTP Method #

The update method requires a resource ID in the URL (e.g., /home/1 for updating the item with ID 1) and either a PUT or PATCH request method.

• If you're using an HTML form: Native HTML forms don't support PUT/PATCH, so you need to use POST with a hidden _method field to spoof the HTTP method. Add these to your form:

  <form action="/home/{{ $yourModel->id }}" method="POST">
      @csrf <!-- Don't forget the CSRF token! -->
      @method('PUT') <!-- Spoofs the PUT method -->
      <!-- Your form fields here -->
  </form>
  

• If you're using AJAX: Make sure your request uses PUT/PATCH as the method, includes the resource ID in the URL, and sends the CSRF token in the request headers (grab it from the <meta name="csrf-token"> tag in your layout).

3. Check for Route Cache Issues #

If you've run php artisan route:cache at any point, Laravel will use a cached version of your routes. Any changes to your routes (like adding a resource controller) won't take effect until you clear the cache:

php artisan route:clear

This is a super common gotcha—always clear the route cache after modifying your routes!

4. Confirm Implicit Model Binding is Set Up Correctly #

If you're using implicit model binding (passing the model directly to your update method), make sure the route parameter name matches the method parameter name:

// Correct: Route parameter is {home}, method parameter is Home $home
public function update(Request $request, Home $home) {
    // Your update logic
}

// Incorrect: Parameter names don't match (would cause 404 if Laravel can't find the model)
public function update(Request $request, Home $id) {
    // This won't work!
}

If the names don't align, Laravel can't resolve the model and will return a 404.

5. Rule Out Permission/Server Configuration Issues #

In rare cases, server configurations (like Apache or Nginx) might block PUT/PATCH requests. For Apache, ensure your .htaccess file includes the Laravel rewrite rules to handle these methods:

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews -Indexes
    </IfModule>

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} (.+)/$
    RewriteRule ^ %1 [L,R=301]

    # Send Requests To Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

For Nginx, confirm your server block includes the try_files directive to pass all requests to Laravel's index.php.

Start with checking the route list and request details first—those are the most frequent fixes. Let me know if any of these steps resolve your issue!

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