#4119: Incorrect HTTP-Date format in expire field of HTTP Header
--------------------------------+-------------------------------------------
Reporter: Ciantic | Owner: adrian
Status: new | Component: Contrib apps
Version: SVN | Resolution:
Keywords: http-date header | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
--------------------------------+-------------------------------------------
Comment (by mtredinnick):
Replying to [comment:6 anonymous]:
> What better patch do I need? Change it to strftime perhaps?
Whichever way you do it, the produced header string should exactly match
the first format shown in section 3.3.1 of the HTTP/1.1 spec. Read the
paragraph just under the examples in that section and you'll see that is
marked as a "MUST" requirement. So whether there is time or datetime
method that does it directly (in a locale-independent fashion) or whether
we have to construct it by hand, that's the format we need to generate.
The important point about that format is that it is always the same number
of characters long. It uses two-digit, zero-padded dates and hour values
and four-digit years, for example.
--
Ticket URL: <http://code.djangoproject.com/ticket/4119#comment:7>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
