You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get that my original code was buggy given RFC 7230 however it was working fine before and isn't anymore which is a breaking change, that why I am raising the issue here.
If you maintainers decide this is a WONTFIX, at least we should convert this issue to something along the lines of net/textproto, mime/multipart: should error when writing invalid part header, it is not normal that I can write thoses broken headers but not read them, if anything this should be consistent.
The text was updated successfully, but these errors were encountered:
Jorropo
changed the title
net/textproto&mime/mimepart: 1.20 regression malformed MIME header line when trying to decode part for binary data in header
net/textproto, mime/mimepart: 1.20 regression malformed MIME header line when trying to decode part for binary data in header
Jun 8, 2023
Jorropo
changed the title
net/textproto, mime/mimepart: 1.20 regression malformed MIME header line when trying to decode part for binary data in header
net/textproto, mime/multipart: 1.20 regression malformed MIME header line when trying to decode part for binary data in header
Jun 8, 2023
seankhliao
changed the title
net/textproto, mime/multipart: 1.20 regression malformed MIME header line when trying to decode part for binary data in header
net/textproto: can write binary header it can't read
Jun 8, 2023
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
1.20.5
(latest release) yes1.19.10
(latest previous release) noWhat operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run https://go.dev/play/p/f3mNQX8WQf6.
What did you expect to see?
What did you see instead?
git bisect
I bisected the issue a6642e6.
RFC 7230
I get that my original code was buggy given RFC 7230 however it was working fine before and isn't anymore which is a breaking change, that why I am raising the issue here.
If you maintainers decide this is a WONTFIX, at least we should convert this issue to something along the lines of
net/textproto, mime/multipart: should error when writing invalid part header
, it is not normal that I can write thoses broken headers but not read them, if anything this should be consistent.The text was updated successfully, but these errors were encountered: