1883055 - [traceback] AttributeError module 'django.middleware.csrf' has no attribute 'REASON_BAD_TOKEN'

Status: RESOLVED FIXED

(Socorro :: Webapp, defect, P2)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Sentry event: https://mozilla.sentry.io/issues/5027347663/events/2ebd7181b6844580ac5b56f62f31708e/

Traceback:

AttributeError: module 'django.middleware.csrf' has no attribute 'REASON_BAD_TOKEN'
  File "django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
  File "django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
  File "__init__.py", line 126, in process_view
    reason = django_csrf.REASON_BAD_TOKEN

Pretty sure this is related to us updating to Django 4.2. I bet the property is different now.

Grabbing this to look into.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

I can reproduce this trivially in a local dev environment:

curl -X POST http://localhost:8000/

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Attachment: [mozilla-services/socorro] bug 1883055: stop using django-session-csrf (#6540)

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

The problem was with django-session-csrf. That library isn't maintained anymore, so I opted to drop it.

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

willkg merged PR [mozilla-services/socorro]: bug 1883055: stop using django-session-csrf (#6540) in ed6cca9.

Comment 5

[Will Kahn-Greene [:willkg] ET needinfo? me]

Since I landed the fix, there have been no further errors. This is only a problem in our staging environment, so I'm going to close it out.