Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

base64 encodings should be line-broken #9

Closed
paulgriffiths opened this issue Aug 10, 2020 · 2 comments
Closed

base64 encodings should be line-broken #9

paulgriffiths opened this issue Aug 10, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@paulgriffiths
Copy link
Contributor

Per section 6.8 of RFC2045 which defines the Content-Transfer-Encoding header:

The encoded output stream must be represented in lines of no more than 76 characters each. All line breaks or other characters not found in Table 1 must be ignored by decoding software.

Currently, no line breaks appear in base64-encoded output.

All base64-encoded output used in a message with a Content-Transfer-Encoding value of base64 should be broken into lines of 76 or less characters.

@paulgriffiths paulgriffiths added the bug Something isn't working label Aug 10, 2020
@paulgriffiths paulgriffiths self-assigned this Aug 10, 2020
@paulgriffiths
Copy link
Contributor Author

Note that RFC 8951 subsequently (in November 2020) updated RFC 7030 to require all endpoints to ignore the value in any Content-Transfer-Encoding header, and to specifically confirm that:

Senders are not required to insert any kind of white space.

@61131
Copy link

61131 commented Dec 18, 2023

PR #31 has been raised to deprecate the Content-Transfer-Encoding header per RFC 8951

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants