Skip to content
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: invalid media parameter #139

Merged
merged 3 commits into from Dec 23, 2019

Conversation

requaos
Copy link
Collaborator

@requaos requaos commented Dec 21, 2019

While we handle media parameters with missing values if they are the last parameter, this fix allows for the handling of media parameters missing value in the middle of the parameter list.

@coveralls
Copy link

coveralls commented Dec 21, 2019

Coverage Status

Coverage increased (+0.03%) to 92.464% when pulling f514da3 on requaos:requaos/missingParameterValue into cf488a7 on jhillyerd:develop.

@requaos requaos self-assigned this Dec 21, 2019
@requaos
Copy link
Collaborator Author

requaos commented Dec 21, 2019

Each of the two above commits, solve a different problem. Both problems result in the same error.

  1. text/html; charset=; format=flowed <-- the middle parameter was not getting fixed
  2. multipart/mixed; boundary=?BE023287982-wefweiuh38839 <-- The first character '?' was not being included in the check to see if the parameter value needs to be quoted.

@jhillyerd jhillyerd merged commit f9d5121 into jhillyerd:develop Dec 23, 2019
@jhillyerd
Copy link
Owner

Thanks.

BTW, I think your test coverage increase may have drawn some recent attention: https://starcharts.herokuapp.com/jhillyerd/enmime

jhillyerd added a commit that referenced this pull request Feb 23, 2020
Added
- Inject a `application/octet-stream` as default content type when none is
  present (#140, thanks requaos)
- Add support for content-type params to part & encoding (#148, thanks
  pzeinlinger)
- UTF-7 support (#17)

Fixed
- Handle missing parameter values in the middle of the media parameter list
  (#139, thanks requaos)
- Fix boundaryReader to respect length instead of capacity (#145, thanks
  dcormier)
- Handle very empty mime parts (#144, thanks dcormier)
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.

None yet

3 participants