Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 19390 invoked by uid 500); 19 Jul 2002 05:31:31 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 19377 invoked from network); 19 Jul 2002 05:31:31 -0000 Message-ID: <3D37A43D.8010406@attbi.com> Date: Thu, 18 Jul 2002 23:31:41 -0600 From: Jerry Baker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020718 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: HTTP 403 served as text/plain References: <3D2E721B.4050405@attbi.com> <3D373563.5356EFF7@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Jul 2002 05:31:41.0682 (UTC) FILETIME=[8FEC6D20:01C22EE5] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Greg Ames says: >Jerry Baker wrote: >> >> Using the current CVS, Apache 2.0.40-dev is sending HTTP 403 messages as >> text/plain. >> >> When I set up a deny from [my ip], I get a plain text message that looks >> like this: >> >> >> >> 403 Forbidden > >yeah, we have hacks on top of hacks in ap_send_error_response and functions it >calls, resulting in content-type being set in the wrong request_req sometimes >when we put out canned error messages. I tried cleaning up some of the hacks a >while back, but it was more complex than I thought. I suppose we could just >focus on getting the content-type and other related fields set in the correct >request_req and make it look prettier at the browser. > >Greg > > > Incidentally, it was fixed at some point after this email, and before 07-16.