8000 Header line incorrectly beginning with a space by requaos · Pull Request #149 · jhillyerd/enmime · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Header line incorrectly beginning with a space #149

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

Merged
merged 1 commit into from
Mar 6, 2020

Conversation

requaos
Copy link
Collaborator
@requaos requaos commented Mar 5, 2020

results in "mime: invalid media parameter" error

This is a best effort attempt to correct an invalid continuation.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 95.587% when pulling eebd72d on requaos:requaos/invalidContinuation into 1147058 on jhillyerd:develop.

@jhillyerd
Copy link
Owner

Looks good, thanks.

@jhillyerd jhillyerd merged commit 2505a64 into jhillyerd:develop Mar 6, 2020
@jhillyerd jhillyerd self-requested a review March 6, 2020 16:07
jhillyerd added a commit that referenced this pull request May 26, 2020
Fixed

- Handle incorrectly indented headers (#149, thanks requaos)
- Handle trailing separator characters in header (#154, thanks joekamibeppu)

Changed

- enmime no longer uses git-flow, and will now accept PRs against master
jhillyerd added a commit that referenced this pull request Oct 31, 2020
This reverts #149 and #166 as we have found them to be unreliable
with real world mail.
jhillyerd added a commit that referenced this pull request Oct 31, 2020
header: revert accidental continuations detection, fixes #171

This reverts #149 and #166 as we have found them to be unreliable
with real world mail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0