Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 12056 invoked by uid 500); 2 Jun 2000 01:54:40 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 12045 invoked from network); 2 Jun 2000 01:54:40 -0000 Date: Thu, 1 Jun 2000 18:54:41 -0700 From: Manoj Kasichainula To: new-httpd@apache.org Subject: Re: SetEnvIf* in .htaccess Message-ID: <20000601185440.A3856@manojk.users.mindspring.com> Mail-Followup-To: new-httpd@apache.org References: <392D469A.18CF991A@Golux.Com> <392D5051.7B987650@raleigh.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.2i In-Reply-To: <392D5051.7B987650@raleigh.ibm.com>; from rederpj@raleigh.ibm.com on Thu, May 25, 2000 at 12:09:53PM -0400 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Thu, May 25, 2000 at 12:09:53PM -0400, Paul J. Reder wrote: > Rodent of Unusual Size wrote: > > > > A while ago I proposed loosening the restriction on SetEnvIf* > > to allow it to be used in .htaccess files (PR#3000). I think the > > only response was from Manoj, wondering if there was any precedent > > for allowing the setting of environment variables in .htaccess > > files. > > > > In fact there is; mod_rewrite can do it (and the rules permit it). > > Actually, you can also legally use SetEnv, PassEnv, and UnsetEnv > in .htaccess files... Then I drop my small amount of worry. Go for it.