Laravel 5.3 Logout MethodNotAllowed

You have to do an http post now so you can't just link to a url, which would be a get. Take a look at the scaffolded auth code to see how Taylor does it.

https://github.com/laravel/framework/blob/7d116dc5a008e69c97f864af79ac46ab6a8d5895/src/Illuminate/Auth/Console/stubs/make/views/layouts/app.stub

Alternatively you can hack it back to how it used to work by adding this route:

Route::get('logout', '\App\Http\Controllers\Auth\LoginController@logout');

Is there a reason this was changed to POST?

Keeps other apps from logging you out. You can read more here... Search for "POST to Logout" - https://laravel.com/docs/5.3/upgrade

Just use this on your route file ..... Route::get('/logout' , 'Auth\LoginController@logout');

That route is handled by Auth::routes()

Here's a way to use the logout as intended. Since the logout route was change to a POST method, you must POST the logout. To do so, use

<li>
    <a href="{{ url('/logout') }}" 
         onclick="event.preventDefault();
         document.getElementById('logout-form').submit();">
          Logout
    </a>
     <form id="logout-form" 
            action="{{ url('/logout') }}" 
        method="POST" 
        style="display: none;">
                    {{ csrf_field() }}
      </form>
</li>

@onamfc solution should be the accepted answer. The accepted answer is a hack that works around the intended reason this change was made.

The posted code is straight from Taylor's github repo here: https://github.com/laravel/framework/blob/7d116dc5a008e69c97f864af79ac46ab6a8d5895/src/Illuminate/Auth/Console/stubs/make/views/layouts/app.stub

The best way to implement this is:

<a href="{{ route('logout') }}" onclick="event.preventDefault(); document.getElementById('logout-form').submit();">Logout</a>

<form id="logout-form" action="{{ route('logout') }}" method="POST" style="display: none;">{{ csrf_field() }}</form>

Since Auth::routes() already comes with name routes, we are using the route() method for this case.

style="display: none;" can be left out as form usually do not show up if there are no visible input fields.

Hello, I have a question: why the href attrib in the a tag is necessary, if the onclick method prevent it and then submit the form?

@juansebas257 without an href attribute many browsers won't underline the link. Also allows a user to hover over the link and see 'logout' in the status bar and provide some reassurance about what will happen.

Breaks without javascript of course...

I started with @ruchern's solution but found it didn't work for me on touch screen devices so had to adapt it a bit, creating an event handler like so:

var submitLogoutForm = function(event) {

    event.stopImmediatePropagation();
    event.preventDefault();
    document.getElementById('logout-form').submit();

};

Then, I assigned the class 'logout-trigger' to the parent nodes of all logout links and attached the event handler with jQuery like so:

$('.logout-trigger').on('click touchstart', submitLogoutForm);

The touchstart event seems to be necessary to capturing what amounts to a click action on mobile devices (or at least on the iPhone). That said, I haven't been able to test it across all/most devices but hopefully it will help others who come on this thread.