Django

Code

Ticket #6219 (closed: wontfix)

Opened 7 months ago

Last modified 7 months ago

HTTP header charset restrictions are too tight

Reported by: mtredinnick Assigned to: nobody
Milestone: Component: Uncategorized
Version: SVN Keywords:
Cc: Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

My reading of RFC 2616 (HTTP/1.1 spec) says that we're being too tough in our HTTP header handling. Section 4.2 says values can include text and quoted strings. Section 2.2 defines text (and quoted strings) to include any octet except some control characters.

Django currently insists that header values are in the ASCII range, which looks to be too small.

(This is a follow-up to #5956).

Attachments

Change History

12/17/07 02:02:10 changed by mtredinnick

  • needs_better_patch changed.
  • stage changed from Unreviewed to Accepted.
  • needs_tests changed.
  • needs_docs changed.

12/17/07 02:27:59 changed by mtredinnick

  • status changed from new to closed.
  • resolution set to wontfix.

Hmm .. upon thinking about this further and discussing it with ubernostrum, I think it's probably not worth doing this. It's not going to be useful in practice (RFC 2047 encoding is generally required and nobody implements the cookie RFCs correctly, which would be the exceptional case). Also, we're going to hit no end of WSGI-related problems (see this old thread for examples of why we can't expect the WSGI maintainers to change their requirements).

Add/Change #6219 (HTTP header charset restrictions are too tight)




Change Properties
Action