Opened 10 years ago

Last modified 12 months ago

#24213 new New feature

RFC 2231 Section 4.1 is not implemented — at Initial Version

Reported by: Raúl Cumplido Owned by: Raúl Cumplido
Component: HTTP handling Version: dev
Severity: Normal Keywords:
Cc: raulcumplido@…, Herbert Fortes, Ülgen Sarıkavak Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Currently RFC 2231 Section 4 is implemented (there is an open PR from me for a fix), but section 4.1 of the RFC is not implemented:
http://tools.ietf.org/html/rfc2231#section-4.1
Section 4.1 is about being able to have parameter continuation when combining Character Set and language Language headers:

Content-Type: application/x-stuff
    title*0*=us-ascii'en'This%20is%20even%20more%20
    title*1*=%2A%2A%2Afun%2A%2A%2A%20
    title*2="isn't it!"

According to the ticket's flags, the next step(s) to move this issue forward are:

  • To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is: [https://github.com/django/django/pull/#### PR].

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top