2 ms·
"The web server also had to be configured to not send a "charset" parameter on the "Content-Type" header, because the old browsers didn't know what to make of t
by yuhong 16y ago
"The web server also had to be configured to not send a "charset" parameter on the "Content-Type" header, because the old browsers didn't know what to make of that. "
Looks like someone messed that up later. From a telnet session to home.mcom.com:
HEAD / HTTP/1.0
HTTP/1.1 200 OK
Date: Mon, 14 Feb 2011 07:57:27 GMT
Server: Apache
Last-Modified: Fri, 21 Oct 1994 19:00:00 GMT
ETag: "10400d9-f1-2c7ebe95f4c00"
Accept-Ranges: bytes
Content-Length: 241
Cache-Control: max-age=31536000
Expires: Tue, 14 Feb 2012 07:57:27 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
- yuhong 16y agoIt is fixed now.