Hosting Provided By

Bug#457339: SetEnv vs. SetEnvif vs. php

From: Stefan Fritsch <sf(at)sfritsch.de>
Date: Sun Dec 30 2007 - 18:25:25 EST

On Friday 21 December 2007, jidanni@jidanni.org wrote:
> meaning that somehow index.php was forgotten
> on the list of things to stop!

I get the complete list of what is listed in DirectoryIndex. Maybe you have a DirectoryIndex statement somewhere that does not list index.php? Did you get "200 OK" or "403 Forbidden"?

> Indeed, one scratches their head about why the effect is not the
> same as the first.

This is likely due to the fact that mod_env and mod_setenvif insert themselves at different phases of the request processing. The end result should be the same, however.

-- 
To UNSUBSCRIBE, email to debian-apache-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Received on Sun Dec 30 18:29:24 2007

This message: [ Message body ]
Next message: Stefan Fritsch: "Bug#458085: apache2.2-common: wrong permissions on /var/lock/apache2"
Previous message: Stefan Fritsch: "Re: cleaner perl printenv"
In reply to: jidanni(at)jidanni.org: "Bug#457339: SetEnv vs. SetEnvif vs. php"
Next in thread: jidanni(at)jidanni.org: "Bug#457339: SetEnv vs. SetEnvif vs. php"
Reply: jidanni(at)jidanni.org: "Bug#457339: SetEnv vs. SetEnvif vs. php"

Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ] [ By messages with attachments ]

This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 02:59:32 EDT