Changes between Initial Version and Version 1 of Ticket #37025, comment 19
- Timestamp:
- May 1, 2026, 11:45:43 AM (3 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #37025, comment 19
initial v1 1 Thanks Mykhailo and Sarah for the illuminating reviews. After checking the history, this is a regression in Django 5.2 (50f89ae850f6b4e35819fe725a08c7e579bfd099) that was not caught in time for a backport. RemoteUserMiddleware's default `REMOTE_USER` value didn't work before that commit, but in fixing the default case, we broke (or "changed the semantic") of the custom header case.1 Thanks Mykhailo and Sarah for the illuminating reviews. After checking the history, this is a regression in Django 5.2 (50f89ae850f6b4e35819fe725a08c7e579bfd099) that was not caught in time for a backport. Under ASGI, RemoteUserMiddleware's default `REMOTE_USER` value didn't work before that commit, but in fixing the default case, we broke (or "changed the semantic") of the custom header case. 2 2 3 3 It was reported in time (#36300), but only as a "hunch", so it was closed as `needsinfo`. I'll reopen and aim to fix in Django 6.1 without a deprecation or a backport, but with a release note.