Ticket #63 (closed design: fixed)
RFC2047 encoded words
|Reported by:||firstname.lastname@example.org||Owned by:|
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.
- Component set to messaging
- Milestone set to unassigned
- Summary changed from Header length limit with encoded words to RFC2047 encoded words
- Status changed from new to closed
- Resolution set to fixed
- Status changed from closed to reopened
- Resolution fixed deleted
- Component changed from p1-messaging to p6-cache
- Milestone changed from 06 to 07