Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 7634 invoked by uid 6000); 17 Feb 1998 06:29:10 -0000 Received: (qmail 7628 invoked from network); 17 Feb 1998 06:29:09 -0000 Received: from paris.ics.uci.edu (mmdf@128.195.1.50) by taz.hyperreal.org with SMTP; 17 Feb 1998 06:29:09 -0000 Received: from kiwi.ics.uci.edu by paris.ics.uci.edu id aa09250; 16 Feb 98 22:24 PST To: new-httpd@apache.org Subject: Re: Accept-Encoding - the saga continues (fwd) In-reply-to: Your message of "Mon, 16 Feb 1998 17:57:57 PST." Date: Mon, 16 Feb 1998 22:16:59 -0800 From: "Roy T. Fielding" Message-ID: <9802162224.aa09250@paris.ics.uci.edu> Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org >I WANT TO SHOOT WHOMEVER CREATED THIS STUPID X- "CONVENTION"!! Join the crowd. The amazing thing is that every six months or so I have to explain to some IETFer why it is so utterly stupid, just so it won't be added to yet another spec. >Anyway, this to me sounds like a case for a BrowserMatch, so I've added >such a beast to the patch. Usage: > >BrowserMatch "MSIE 4\." strip-ce-header > >If strip-ce-header set, the fixup handler will remove any Content-Encoding >header that might have been set. Note that I'm not sure exactly which >versions of MSIE exhibit this problem. Also, I think this should be put in >the known_client_problems page, and not as a part of the default srm.conf . Nope, -1 on this part. There is never going to be a browser bug which is so bad that it forces Apache to knowingly send the wrong HTTP fields. If the C-E is removed, the Content-Type must be changed. ....Roy