fix: add UTF-8 charset to OAuth callback HTML responses - #17
Merged
Conversation
The checkmark (✓) and cross (✗) characters in the auth success/error pages displayed as mojibake in browsers due to missing charset declaration. Add charset=utf-8 to Content-Type headers and meta charset tags to HTML. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 task
scottlovegrove
approved these changes
Jan 22, 2026
Collaborator
|
Thanks! |
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
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.
Fixed character encoding issue in OAuth callback pages where checkmark (✓) displayed as "âœ""
Test plan
td auth login