Opened 12 years ago

Closed 10 years ago

#63 closed design (fixed)

RFC2047 encoded words

Reported by: mnot@… Owned by:
Priority: Milestone: 07
Component: p6-cache Severity:
Keywords: Cc:

Description

RFC 2616 defines RFC 2047 MIME word encoding for use with certain header values, e.g. if they are defined to contain quoted strings. RFC 2047 states:

While there is no limit to the length of a multiple-line header field, each line of a header field that contains one or more 'encoded-word's is limited to 76 characters.

The length restrictions are included both to ease interoperability through internetwork mail gateways, and to impose a limit on the amount of lookahead a header parser must employ (while looking for a final ?= delimiter) before it can decide whether a token is an "encoded-word" or something else.

It seems to me this provision is not meant to apply to HTTP, and if MIME word encoding is to stay with us in the next HTTP specification, it should state that this line length limit does not apply to HTTP.

Change History (10)

comment:1 Changed 12 years ago by mnot@…

  • Component set to messaging
  • Milestone set to unassigned

comment:2 Changed 11 years ago by mnot@…

Also includes:

  • should the set of character encodings be restricted?
  • should the encoding form (b or q) be restricted?
  • should line folding be addressed?

comment:3 Changed 11 years ago by mnot@…

  • Summary changed from Header length limit with encoded words to RFC2047 encoded words

comment:4 Changed 11 years ago by mnot@…

Proposal:

Only remove the line length restrictions.

comment:5 Changed 11 years ago by mnot@…

  • Milestone changed from unassigned to 06

comment:6 Changed 11 years ago by fielding@…

From [395]:

Deprecate line folding, addresses #77. Require that invalid whitespace around field-names be rejected, addresses #30. Make non-ASCII content obsolete and opaque in header fields and reason phrase, addresses #63, #74, #94, #111.

comment:7 Changed 11 years ago by julian.reschke@…

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [398]:

Resolve #63, #74, #94, #111: Issues around TEXT rule closed with revision [395] (closes #63, #74, #94, #111)

comment:8 Changed 11 years ago by julian.reschke@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

re-open until reviewed

comment:9 Changed 10 years ago by julian.reschke@…

  • Component changed from p1-messaging to p6-cache
  • Milestone changed from 06 to 07

Part 6 still allows RFC2047 encoding for the Warn header.

comment:10 Changed 10 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.