Dean,
Even if this is correct behavior, there should at least be a note
that warns people against this, and/or Apache should catch this and not
spin off into infinite doom when a request comes in. Even if it's just
an absolute fail safe directive that limits how many levels deep you can
perform a subrequest.
I could not find anywhere something that says that action prepends the URI
to the request and issues a subrequest, which is then (again) matched
against LocationMatch/DirectoryMatch blocks. Unless you are familiar with
Apache internals, there's no way you could even *guess* that this would
happen.
Our configuration is not broken, this is actually a real requirement for
our site. In the end, we ended up doing a mod_rewrite hack to fix this.
Max Campos
On 20 Apr 1999 [EMAIL PROTECTED] wrote:
> Synopsis: DirectoryMatch/LocationMatch fail when used with SetHandler & Action
>
> State-Changed-From-To: open-closed
> State-Changed-By: dgaudet
> State-Changed-When: Tue Apr 20 10:11:21 PDT 1999
> State-Changed-Why:
> Yes, of course that happens. It matches a /one/, then it
> prepends your Action handler to the URI and re-runs the
> access checks.
>
> Then it matches a /one/ and prepends your Action handler to
> the URI and re-runs the access checks.
>
> Then it matches a /one/ ...
>
> Your configuration is broken.
>
> Dean
>
