Add Content-Type header to report/mail.go . #280
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
Closed
(fix pull request, "utf8" to "utf-8".) I did the following test. - compile vuls with this fix. - I executed the following command and confirmed that garbled display is not done. + vuls scan -lang=en -report-mail -cve-dictionary... + vuls scan -lang=ja -report-mail -cve-dictionary... Mail header is as follows. Message-Id: <...> Subject: <...> Content-Type: text/plain; charset=utf8 From: <...> To: <...> Cc: <...>
|
Checked RFC and changed utf8 to utf-8. I tested it as follows.
|
|
Many thanks! |
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.
Vuls report mail has NO charset header.
This pull request contain 'Content-Type: text/plain; charset=utf8' header.