[Django] #35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong HTTP method

[Django]

#35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong
HTTP method
-------------------------------------------+------------------------
Reporter: venteto | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 5.0
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+------------------------
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.

--
Ticket URL: <https://code.djangoproject.com/ticket/35013>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

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

---------------------------------+--------------------------------------

Reporter: venteto | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 5.0

Severity: Release blocker | Resolution:

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

---------------------------------+--------------------------------------
Changes (by venteto):

* Attachment "Screenshot from 2023-12-05 00-57-25.png" added.

[Django]

#35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong
HTTP method
---------------------------------+--------------------------------------

Reporter: dg | Owner: nobody
Type: Bug | Status: closed

Component: HTTP handling | Version: 5.0

Severity: Release blocker | Resolution: invalid

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------

Changes (by David Sanders):

* status: new => closed
* resolution: => invalid

Comment:

Hi,

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

--
Ticket URL: <https://code.djangoproject.com/ticket/35013#comment:1>

[Django]

#35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong
HTTP method
---------------------------------+--------------------------------------
Reporter: dg | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 5.0
Severity: Release blocker | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------

Comment (by dg):

Replying to [comment:1 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.

--
Ticket URL: <https://code.djangoproject.com/ticket/35013#comment:2>

[Django]

#35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong
HTTP method
---------------------------------+--------------------------------------
Reporter: dg | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 5.0
Severity: Release blocker | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------

Comment (by 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/

--
Ticket URL: <https://code.djangoproject.com/ticket/35013#comment:3>

[Django]

#35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong
HTTP method
-------------------------------+--------------------------------------
Reporter: dg | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 5.0

Severity: Normal | Resolution: invalid

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

-------------------------------+--------------------------------------
Changes (by Natalia Bidart):

* severity: Release blocker => Normal

--
Ticket URL: <https://code.djangoproject.com/ticket/35013#comment:4>