Improved docs regarding UTF-8 support with Apache and mod_wsgi. #14944
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.
When I first set up Django on a Linux server, I found that configuring mod_wsgi and Apache to support UTF-8 files was tricky. The current Django documentation could be improved with (a) an additional example of how to configure mod_wsgi, and (b) to clarify that files with non-ASCII content (and not just files with non-ASCII file names) can be affected.
This PR is to update the docs in a couple of places for this purpose.
The example I added comes from this blog post: