From: dgaudet Date: Mon, 25 May 1998 04:21:56 +0000 (+0000) Subject: add a note about the content-type reload bug, and a few copy-edit tweaks X-Git-Tag: djg-apache-nspr-07~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=46b7616435343b850827b4a7dbeab5afbb199443;p=thirdparty%2Fapache%2Fhttpd.git add a note about the content-type reload bug, and a few copy-edit tweaks git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@81358 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/known_client_problems.html b/docs/manual/misc/known_client_problems.html index 63336e8a657..db80d6e7500 100644 --- a/docs/manual/misc/known_client_problems.html +++ b/docs/manual/misc/known_client_problems.html @@ -16,17 +16,18 @@

Known Problems in Clients

Over time the Apache Group has discovered or been notified of problems -with various clients which we have had to work around. This document -describes these problems and the workarounds available. It's not arranged -in any particular order. Some familiarity with the standards is assumed, -but not necessary. +with various clients which we have had to work around, or explain. +This document describes these problems and the workarounds available. +It's not arranged in any particular order. Some familiarity with the +standards is assumed, but not necessary.

For brevity, Navigator will refer to Netscape's Navigator -product, and MSIE will refer to Microsoft's Internet Explorer -product. All trademarks and copyrights belong to their respective -companies. We welcome input from the various client authors to correct -inconsistencies in this paper, or to provide us with exact version -numbers where things are broken/fixed. +product (which in later versions was renamed "Communicator" and +various other names), and MSIE will refer to Microsoft's +Internet Explorer product. All trademarks and copyrights belong to +their respective companies. We welcome input from the various client +authors to correct inconsistencies in this paper, or to provide us with +exact version numbers where things are broken/fixed.

For reference, RFC1945 @@ -135,8 +136,8 @@ HREF="http://www.apache.org/dist/patches/apply_to_1.2.1/msie_4_0b2_fixes.patch" have a problem if the trailing CRLF of the response header starts at offset 256, 257 or 258 of the response. A BrowserMatch for this would match on nearly every hit, so the workaround is enabled automatically -on all responses. The workaround is to detect when this condition would -occur in a response and add extra padding to the header to push the +on all responses. The workaround implemented detects when this condition would +occur in a response and adds extra padding to the header to push the trailing CRLF past offset 258 of the response.

Multipart responses and Quoted Boundary @@ -244,6 +245,21 @@ BrowserMatch "Java1\.2beta[23]" nokeepalive is usually not a good idea; ideally it gets fixed, new betas or a final release comes out, and no one uses the broken old software anymore. In theory. +

Content-Type change +is not noticed after reload

+ +

Navigator (all versions?) will cache the content-type +for an object "forever". Using reload or shift-reload will not cause +Navigator to notice a content-type change. The only +work-around is for the user to flush their caches (memory and disk). By +way of an example, some folks may be using an old mime.types +file which does not map .htm to text/html, +in this case Apache will default to sending text/plain. +If the user requests the page and it is served as text/plain. +After the admin fixes the server, the user will have to flush their caches +before the object will be shown with the correct text/html +type. +