Add UTF-8 charset to text response content types#105
Merged
GeekInTheNorth merged 1 commit intoJun 15, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR updates the Content-Type headers for llms.txt and robots.txt responses from
text/plaintotext/plain; charset=utf-8.This makes the response encoding explicit for clients consuming these text files.
I have targeted
developbecause the repository appears to use it as the integration branch.The change should also be relevant for the older CMS 12 / .NET 8 line. I am happy to create a separate backport PR if there is a maintained branch for that version.