Comment by tlrobinson
16 years ago
Yeah...
Content-Type: text/plain; charset=ISO-8859-1
Interesting that Safari is "smart" and ignores the content type in this case.
16 years ago
Yeah...
Content-Type: text/plain; charset=ISO-8859-1
Interesting that Safari is "smart" and ignores the content type in this case.
My Safari printed the raw HTML source at first, but rendered the HTML upon reload.
Yeah, mine too. I'm almost motivated to go look why... but not quite.
I looked for a 'View as' menu item prior to reloading, but very interesting that a reload fixed it.
Strange, same on android but I wouldn't have thought to refresh.
Another interesting thing is exploring being pedantically standards compliant (breaking usefulness sometimes) versus bending standards (in the expense of encouraging bad practice)
Good old Postel's Law.
If all browsers actually paid attention to Content-Type then this site probably would have fixed the actual problem. Instead we have a world where it works in only some browsers, and naïve users consider the one that is technically more correct to be "broken".
Didn't know about this, thanks. Further reading: Two viewpoints:
http://diveintomark.org/archives/2004/01/08/postels-law
http://www.dynamicobjects.com/d2r/archives/002518.html
View -> Text Encoding -> Autodetect.
This seems to resolve the issue well enough.