Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Date: Mon, 8 Jan 2007 18:01:51 +0000
From: Nick Kew <nick@webthing.com>
To: modules-dev@httpd.apache.org
Subject: Re: Need help with ErrorDocument
Message-ID: <20070108180151.722a6bab@grimnir>
In-Reply-To: <dc2a864c0701080653h6b03e615xae1e51c7d18aba37@mail.gmail.com>
References: <dc2a864c0701080653h6b03e615xae1e51c7d18aba37@mail.gmail.com>
Organization: WebThing
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 8 Jan 2007 20:23:26 +0530
"Vedavyas Raichur" <vedavyasraichur@gmail.com> wrote:

> Hi All,
>          I am new to apache & facing the following problem:
> 
> 1. A custom module that does client authentication on top of mod_ssl
> returns a FORBIDDEN when user is not authenticated.

That's probably not what you want.  FORBIDDEN means there's nothing
the client can do, which is not the case when the failure is one
of authentication.

>	 But when the
> server tries to fetch the custom ErrorDocument for this error it is
> FORBIDDEN again by same module above.

Yep.

> Is there any known solution to tackle this recursion.

The simple solution is for the ErrorDocument to be kept outside the
scope of what's restricted by your module.  That gives control to
system administrators.

-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/