-
Notifications
You must be signed in to change notification settings - Fork 18k
mime/multipart: leading whitespace is trimmed #5295
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
Labels
Milestone
Comments
I haven't looked into this yet, but in any case it's too late for Go 1.1. In our previous debugging we've found that no two MIME and/or quoted-printable implementations tend to do the same thing. If we're in violation of the RFC and also other popular implementations, we should fix this. But I haven't read the specs or looked at your examples yet. Labels changed: added packagebug, removed priority-triage. Status changed to Accepted. |
Fix out for review: https://golang.org/cl/8536045 This would normally be too late given the Go 1.1 freeze (http://golang.org/s/go11freeze) but I would argue this is a pretty bad regression from Go 1.0. Labels changed: added go1.1. Status changed to Started. |
This issue was closed by revision 24555c7. Status changed to Fixed. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Attachments:
The text was updated successfully, but these errors were encountered: