Documented Content-Transfer-Encoding
#16
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mklocek
reviewed
Sep 25, 2023
i7an
force-pushed
the
iy/document-content-transfer-encoding
branch
from
1128389
to
9b3f1ea
Compare
leveldorado
approved these changes
Sep 26, 2023
mklocek
approved these changes
Sep 26, 2023
IgorDobryn
approved these changes
Sep 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
There where a couple of complains about
Content-Transfer-Encoding. I tried to elaborate on what to expect and what not from this gem.Changes
Content-Transfer-EncodingHow to test
N/A