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

update misleading info about default charset in HTTP (fixes #426) #429

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from

Conversation

reschke
Copy link

@reschke reschke commented Nov 11, 2022

This text really needs a rewrite; it apparently hasn't been touch for nearly two decades. This PR applies a minimal fix WRT defaults that do not exist in HTTP anymore.

This text really needs a rewrite; it apparently hasn't been touch for nearly two decades. This PR applies a minimal fix WRT defaults that do not exist in HTTP anymore.
@netlify
Copy link

netlify bot commented Nov 11, 2022

Deploy Preview for i18n-drafts ready!

Name Link
🔨 Latest commit 2578990
🔍 Latest deploy log https://app.netlify.com/sites/i18n-drafts/deploys/636e98de37af650008d04385
😎 Deploy Preview https://deploy-preview-429--i18n-drafts.netlify.app/articles/http-charset/index.en
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Copy link
Contributor

@aphillips aphillips left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I'm going to create a tracking issue for a more thorough fixup.

ISO-8859-1. But there are too many unlabeled documents in other encodings, so browsers use the reader's preferred encoding when there is no explicit
<p>Documents transmitted with HTTP that are of type text, such as text/html, text/plain, etc., can send a <a class="print" href="https://www.rfc-editor.org/rfc/rfc9110#field.content-type">charset parameter</a> in the HTTP header to specify the character encoding of the document. </p>
<p>It is <strong>very important</strong> to always label Web documents explicitly. Until 2014 (RFC 7231), HTTP/1.1 used to say that the default charset is
ISO-8859-1. But there are too many unlabeled documents in other encodings, so browsers either detect the encoding based on the MIME type, or otherwise use the reader's preferred encoding when there is no explicit
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't quite correct, but to your point this needs a thorough rewrite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants