-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
mime/multipart: add (*Reader).NextRawPart to bypass automatic quoted-printable handling #29090
Comments
To be clear, the signature would be |
Still SGTM. |
Change https://golang.org/cl/152877 mentions this issue: |
As far as I can tell, this is ready to go still. The issue has the labels "help wanted" and "needs fix". Might want to double check whether those are still valid. Would love to take this off my todo list. |
Change https://golang.org/cl/217128 mentions this issue: |
Updates #29090 Updates #36878 Change-Id: I63f0eb583285d5c12f591cb704097cdf6a67b64f Reviewed-on: https://go-review.googlesource.com/c/go/+/217128 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
https://play.golang.org/p/7x85EhvIbZZ
What did you expect to see?
I expected the part headers to include the
Content-Transfer-Encoding
as-is, and for the part body reader to return content as-is.What did you see instead?
I found that
Part
has special handling for parts withContent-Transfer-Encoding: quoted-printable
, which as introduced in issue #4411.GitHub has also just led me to issue #26803 (which I failed to find before) which also proposes a way to bypass this via
Part.NextRawPart
. Unfortunately, although that proposal was accepted, the issue was closed by the submitter before being implemented.Having access to the raw part body and unmodified headers is useful. In particular, for an IMAP server, I need to be able to inspect the part headers and body, including the
Content-Transfer-Encoding
header, in order to build the BODYSTRUCTURE response.I can think of a couple workarounds for my particular server but they're not great, and I think this deserves a fix in the std library.
The text was updated successfully, but these errors were encountered: