Reverted RFC 2047 encoding support for HTTP header field parameters has been removed

Published: | Categories: Miscellaneous | Creative Commons BY-SA 3.0


When decoding the filename parameter in Content-Disposition headers, Firefox had attempted to unescape using the RFC 2047 encoding. This was a bug according to the relevant specs, and implemented only on Firefox and Chrome. The RFC 2231 and RFC 5987 encodings can be used instead.

Update: This change has been postponed to collect and analyze data on the usage of the RFC 2047 encoding.