LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong HTTP method

[dg]

It seems to be sending a GET request, which leads to a 405 error, and no logout occurs, no loading of a custom logout template occurs.

[David Sanders]

Hi,

Thanks for the report, though LogoutView does not accept GET requests – this is intentional :)

[dg]

Replying to David Sanders:

Hi,

Thanks for the report, though LogoutView does not accept GET requests – this is intentional :)

I understand that, but I'm not sending a GET request. If I revert the Django version to 4.2, there is no error. It seems like something in Django 5 is sending the wrong request. I didn't change anything other than upgrading Django.

[David Sanders]

I understand that, but I'm not sending a GET request. If I revert the Django version to 4.2, there is no error. It seems like something in Django 5 is sending the wrong request. I didn't change anything other than upgrading Django.

Sure, but we can't action anything based on this information unfortunately 🤷‍♂️ The best course of action is to determine what's sending the request, then if you find something concrete that indicates Django is at fault please feel free to provide more details here and reopen the ticket.

You can seek assistance from one of the Django support channels where there are many friendly people that can help you: ​https://www.djangoproject.com/community/

Lastly just to clarify the release notes for removed features (including logout via GET) are documented here: ​https://docs.djangoproject.com/en/5.0/releases/5.0/