Closed Bug 295084 Opened 17 years ago Closed 6 years ago

need to move RFC 2047 (and 2231) encoding routines out of mailnews

Categories

(Core :: Networking, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jshin1987, Assigned: jshin1987)

References

(Blocks 2 open bugs)

Details

(Keywords: intl)

RFC 2047 and RFC 2231 encoding routines are needed outside mailnews. For
instance,  RFC 2388 specify that RFC 2047 encoding be used for name and filename
parameters of Content-Disposition header field (http://www.ietf.org/rfc/rfc2388
) [1] in multipart/form-data. 

RFC 2047/2231 decoding routines were moved to necko out of mailnews 2 years ago.
 We may have to extend or revise the interface (for decoding) to support encoding. 

Btw, there's a bug depending on this bug, but I forgot which one is.

[1] I think it's an error to say that RFC 2047 be used, but perhaps it's too
late to fix it.
Summary: need to move RFC 2047 (and 2231) encoding routines out of mailnews → need to move RFC 2047 (and 2231) encoding routines out of mailnews
Blocks: 136676
(In reply to comment #0)
> RFC 2047 and RFC 2231 encoding routines are needed outside mailnews. For
> instance,  RFC 2388 specify that RFC 2047 encoding be used for name and filename
> parameters of Content-Disposition header field (http://www.ietf.org/rfc/rfc2388
> ) [1] in multipart/form-data. 

I thought RFC 2388 says that name (from a field name in the form) in
Content-Type disposition header may use RFC 2047 encoding and RFC 2231 encoding
mighe be used for file names when there is file input/upload in multipart/form.
Indeed. I found, in another bug, that RFC 2388 has such a provision after
writing my previous comment. Thanks for your reminder, though.

Blocks: 323109
Blocks: 41489
I think this bug can be closed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.