Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

text/plain content-type should be charset=utf-8 #1647

Closed
ietf-svn-bot opened this issue Mar 26, 2015 · 3 comments
Closed

text/plain content-type should be charset=utf-8 #1647

ietf-svn-bot opened this issue Mar 26, 2015 · 3 comments

Comments

@ietf-svn-bot
Copy link

resolution_fixed type_defect | by dkg@fifthhorseman.net


https://datatracker.ietf.org/meeting/92/agenda/saag/ produces a UTF-8-encoded text agenda.

But the Content-Type: is just text/plain with no charset. Most tools assume that the default charset is iso-8859-1, with the result that:

Jan Včelák/NSEC5

renders as:

Jan V�elák/NSEC5

Issue migrated from trac:1647 at 2022-03-04 04:32:41 +0000

@ietf-svn-bot
Copy link
Author

@henrik@levkowetz.com changed status from new to closed

@ietf-svn-bot
Copy link
Author

@henrik@levkowetz.com changed resolution from `` to fixed

@ietf-svn-bot
Copy link
Author

@henrik@levkowetz.com commented


Fixed in 2f54511:

Changed all explicitly set HttpResponse content_types to specify charset.
Django sets charset if you don't specify a content_type; if you specify
one you also must add a charset specification (if you want one).

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant