- From: David Norris <kg9ae@geocities.com>
- Date: Wed, 2 Sep 1998 02:44:25 -0500
- To: <w3c-wai-ig@w3.org>
>To display the document correctly, browsers have to know the character >encoding of the document. If the proper character encoding information >is provided via HTTP header, browsers are able to know how to display >the document *before* parsing the document. But if the character >encoding information is only available via HTTP-EQUIV, browsers have >to parse the document to know that information, then try to display >the document again. That's one of the disadvantages of HTTP-EQUIV. I understand this much. But, I am not really sure why it must retrieve the document twice from the server. I would think that once it parses the EQUIV it could just parse the same file over again. The data shouldn't have changed. But, that is where I am unsure. Maybe the data is changed somehow before it is written to the cache. In any case, correct headers are most definitely preferable. I have never looked inside a browser. I have been inside Apache quite a bit, though. The language negotiation is a bit baffling, though. It is so simple, yet, so complex. ,David Norris World Wide Web - http://www.geocities.com/CapeCanaveral/Lab/1652/ Illusionary Web - http://illusionary.dyn.ml.org/ <-- 02:00 - 10:00 GMT Video/Audio Phone - callto:illusionary.dyn.ml.org Page via mail - 412039@pager.mirabilis.com ICQ Universal Internet Number - 412039 E-Mail - kg9ae@geocities.com
Received on Wednesday, 2 September 1998 03:44:09 UTC