id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
28690	django.utils.http.parse_http_date two digit year check is incorrect	Mads Jensen	Ad Timmering	"RFC 850 does not mention this, but in RFC 7231 (and there's something similar in RFC 2822), there's the following quote:

   Recipients of a timestamp value in rfc850-date format, which uses a
   two-digit year, MUST interpret a timestamp that appears to be more
   than 50 years in the future as representing the most recent year in
   the past that had the same last two digits.

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."	Bug	closed	Utilities	dev	Normal	fixed		Ad Timmering	Accepted	1	0	0	0	1	0