4 ms·
HTTP has good support for declaring content encoding. Putting this in HTML probably seems like wasted bytes to protocol purists.
by timClicks 12y ago
HTTP has good support for declaring content encoding. Putting this in HTML probably seems like wasted bytes to protocol purists.
- andyroid 12y agoOne advantage of putting it in a meta tag is that the encoding is preserved even if the document is read from elsewhere (parsed from the local filesystem, etc).
- vardump 12y agoNot to mention that not everyone has control over what HTTP headers get sent. It's way easier for a non-technical person to just add it in meta tag. Definitely a lot better option than leaving the matter to browser encoding sniffer!