Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of matt.farey@gmail.com
 designates 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=MHZN/Pkpi8JDiCtIuzdIMQDEQ7PLPxhpAzVPasow0AOwccJuszJi0hh64I0AeXuT+7I81ZJFkQR+HAI90AnRIHGVrg+2qkP0UvzjIDVjQDsxlDcTwdVA7VVPPeVvkkyQtnL8DjxzaiQiNod5FFV2ld5llNOcyn6RUb6bgPhBoQY=
Message-ID: <45F048D8.8060705@gmail.com>
Date: Thu, 08 Mar 2007 17:33:12 +0000
From: matt farey <matt.farey@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: users@httpd.apache.org
References: <89D56563-B072-4183-BFCF-6A6818651E34@frontierflying.com>
 <813716b60703071048l2cee51e4m48091ab9b85db8be@mail.gmail.com>
 <7A39686F-24E0-4002-8C53-607C3B93524F@frontierflying.com>
 <813716b60703071248h61b6f5ej65d659ca46c3fdff@mail.gmail.com>
 <56F8F0E0-B96E-428A-AFC0-5943C4651945@frontierflying.com>
 <813716b60703071416wcfb2e73i9b936a0d4ce703fa@mail.gmail.com>
 <FC8C341D-7017-45F5-A2C5-3A998ACA12C7@frontierflying.com>
 <813716b60703071638j54c9d7b4xc3e6fc1bdc348a90@mail.gmail.com>
 <1D6EAB93-4101-452E-9CEE-C54EE745D4C1@frontierflying.com>
In-Reply-To: <1D6EAB93-4101-452E-9CEE-C54EE745D4C1@frontierflying.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] mod_rewrite problem


Israel Brewster wrote:
> Just got a response from the developer of the PHP script
> (serendipity). Turns out the problem lies there, and not with the
> rewrite rule. Apparently what's going on is that the php script uses
> the REQUEST_URI to determine what to display. If it doesn't recognize
> the REQUEST_URI (as is the case with /nagios) it just displays the
> main page. It would appear that while mod_rewrite successfully
> rewrites the URL and calls the PHP script, it doesn't actually change
> the REQUEST_URI, so the script is still acting on /nagios, which it
> doesn't recognize. I'll admit this is somewhat beyond me at the
> moment, perhaps I need to look more into the difference between the
> REQUEST_URI that the php script is seeing and what, exactly,
> mod_rewrite is changing. At any rate, that at least explains the problem.
>
yeah, if you compare the number and type of rewrites for this package
with the way that wordpress used to operate, there is a lot of
correlation, instead now wordpress uses a much simpler form of rewrite
which directs the REQUEST_URI to the application for subsequent
alteration, as is the case with your serendipity app. My idea would be
to handle all the serendipity rules with the app, leaving a much smaller
set of rules which would happily coexist and be easy to modify. I know
you say you aren't a php developer, but it wouldn't be that hard to
locate and alter the script, perhaps though it would be difficult to
subsequently update Serendipity and you would feel this would be a step
too far. my $0.02 - when wordpress changed their rewrite rules from 2k 
down to  4 lines it was great!

-- 
Matthew Farey


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org