django__django-11848

django.utils.http.parse_http_date two digit year check is incorrect

Verdict: the fix is stated in the issue (Tier A).

Accepted, however I don't think your patch is correct. The check should be relative to the current year, if I read the RFC quote correctly.

The text states the fix: “Current logic is hard coded to consider 0-69 to be in 2000-2069, and 70-99 to be 1970-1999, instead of comparing versus the current year.”

All SWE-bench Verified tasks · more django/django tasks · How the check works