(PTFE-2500) Nginx should use charset utf8 #207
Merged
Conversation
This file contains hidden or 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
matthiasL-scality
force-pushed
the
PTFE-2500-add-artifact-get-utf8
branch
2 times, most recently
from
b0b1075 to
a8d179c
Compare
matthiasL-scality
force-pushed
the
PTFE-2500-add-artifact-get-utf8
branch
from
a8d179c to
03e9f66
Compare
cmeron
approved these changes
Jul 22, 2025
mcolzi
reviewed
Aug 12, 2025
| done | ||
| done | ||
| echo ".log text/plain;" >> /etc/nginx/mimetypes.map | ||
| echo " .log \"text/plain; charset=utf-8\";" >> /etc/nginx/mimetypes.map |
There was a problem hiding this comment.
Do you confirm the space before ".log" ?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Purpose
Some logs are not well encode, we should specify charset=utf8 to display them