php/cgi URI parsing problem...

aarobonob

Hello,

I have searched and not found the answer. I hope you could help.

I have two php scripts.
/read
/profile

both do not have extensions. They parse $_SERVER['REQUEST_URI'] for the info... for example...
/read/username/articleID

NOw, this worked fine with an .htaccess file forcing the type on a mod_php configuration. NOw with PHP-CGI, it does not work correctly.

I have tried many different things... the closest I got was:
/read
which generated the php page.
but...
/read/username
would do an error 500..t he closest answer was redirect the error 500 script..or copy it as /read.. and then rewrite something.

but this will nto work because I have two scripts!

Any suggestions woudl be greatly apprecaited.
-Aaron

superwormy

I tried this for a LOOONNNNG time with CGI, and never got it to work. If you can get it to work, let me know how.

It seems the CGI doesn't walk back down URLs like Apache with mod_php does.

sglane

Possibly rename the files back to .php and use Apache's mod_rewrite to send you what you need. That's what most people do, but mod_rewrite can be very confusing.

aarobonob

This is what we had to do.

/read script
(parses QUERY_STRING)

/profile script
(parses QUERY_STRING)

.htaccess
<Files read>
ForceType php-script
</Files>

Options +SymlinksIfOwnerMatch
RewriteEngine On
RewriteBase /
RewriteRule ^read/(.*)$ /read?$1

<Files profile>
ForceType php-script
</Files>

Options +SymlinksIfOwnerMatch
RewriteEngine On
RewriteBase /
RewriteRule ^{profile/(.*)$} /profile?$1

what happens is it takes anything after the / after profile and makes it the query after the ?

not a perfect solution, but the best one yet 🙂

-Aaron