Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4A031EB4.1020501@cablewholesale.com>
Date: Thu, 07 May 2009 10:47:32 -0700
From: "Michael A. Capone" <mcapone@cablewholesale.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.1.19) Gecko/20081204 Firefox/2.0.0.17
MIME-Version: 1.0
To: mod_perl <modperl@perl.apache.org>
Subject: Re: ErrorDocument from a registry script
References: <4A02FA96.6070209@plusthree.com>
In-Reply-To: <4A02FA96.6070209@plusthree.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

In the spirit of checking off the obvious things... are you sure that 
the ErrorDocument directive is working for other pages?  in other words, 
can you open a browser and goto 
http://mydomain.com/this_file_does_not_exist.htm and see your ErrorDocument?

Michael Peters wrote:
> I'm pretty sure this should just work and I'm doing something stupid, 
> so any helpful insults that point me in the right direction would be 
> appreciated :)
>
> I have a registry script that could return a NOT FOUND (404) error. 
> I'm handling that like so:
>
>   Apache->request->status(NOT_FOUND);
>
> The browser does get the 404 HTTP status header, but it does not 
> trigger the ErrorDocument 404 that is set up, instead just showing the 
> browser's built-in 404 message. PerlSendHeaders is Off and I'm not 
> printing any output.