MierMier wrote:
>
>
>
> MierMier wrote:
>>
>> Hey people, I need your help, thanks in advance!
>>
>> I have an appche server 2.x. + PHP, And I woundered rather it is possible
>> to output the same page (i.e. "a.php") for a request of what
Well thanks alot, but somhing went wrong, and after reading, still can't
understand why.
I have an Apache server server on my PC, based on WinXP,
and when I use these in .htaccess
Options +FollowSymLinks
RewriteEngine On
RewriteRule ^.*$ /a.php [QSA]
it works well.
How ever at my Linux
MierMier wrote:
>
> Hey people, I need your help, thanks in advance!
>
> I have an appche server 2.x. + PHP, And I woundered rather it is possible
> to output the same page (i.e. "a.php") for a request of whatever page.
>
> I will give an examples:
>
&g
Brian Mearns-2 wrote:
>
> The QSA option is what you need to pass the GET arguments along to the
> rewritten url. For instance, if you want EVERY url to get served by
> a.php, including GET arguments, you can do:
>
> RewriteRule ^.*$ /a.php [QSA]
>
>
> I'm pretty sure that's the writ
MierMier wrote:
>
>
>
> Justin Pasher wrote:
>>
>> MierMier wrote:
>>> Hey people, I need your help, thanks in advance!
>>>
>>> I have an appche server 2.x. + PHP, And I woundered rather it is
>>> possible
>>> to output t
Justin Pasher wrote:
>
> MierMier wrote:
>> Hey people, I need your help, thanks in advance!
>>
>> I have an appche server 2.x. + PHP, And I woundered rather it is possible
>> to output the same page (i.e. "a.php") for a request of whatever page.
>
Hey people, I need your help, thanks in advance!
I have an appche server 2.x. + PHP, And I woundered rather it is possible
to output the same page (i.e. "a.php") for a request of whatever page.
I will give an examples:
if the client try to reach "/hello/index.php" (which do not really exist in
