[suPHP] No search engine friendly URLs anymore?
Christian Scholz-Flöter
cs at christianscholz.com
Wed May 7 12:26:44 CEST 2008
> This is a very bizare .htaccess, if you ask me. <Files> is supposed
> to be used to refer to actual files/filenames, not directories or
> pieces of a directory.
In fact, articles and topics are extensionless PHP files in my domain's
root folder. The htaccess had the task to redirect URLs containing
"articles" or "topics" to those PHP files. Inside, I checked the
path_info, counted the arguments and finally glued together the page
that should be displayed.
I read about this somewhere on the internet some years ago and it used
to worked fine.
> You probably have directories on the filesystem called /articles/ and
> /topics/, and inside each you have an index.php file which is doing
> the URL re-writing for you. The PHP script is examining the
> REQUEST_URI environment variable, or something very similar to that,
> and does some magic to map it to something internal that will return
> results for what you want.
Almost ;)
> ForceType is forcing the MIME type of all files within those
> directories to be application/x-httpd-php, and I don't understand why
> this is being used, unless your hosting provider gives you the
> opportunity to "opt-in" to using suPHP.
No, sadly, I obviously have to live with my provider's decision and to
find a way around the trouble that it's causing me.
> If your provider is recommending this, they have no idea what they're
> doing.
The one support guy who wrote back to me admitted exactly that. It's
like I had bought a car from them, used it for a while and enjoying
myself, but then they decided to make my(!) car not run on gas anymore
and leave me alone with the situation.
> I don't see what suPHP has to do with re-writing URLs. There's
> nothing about suPHP which stops a PHP script from running when an
> HTTP request is received, and mapping something "simple" like
> "foo-bar-blat" into something internally like
> "blah.php?name=foo%20bar%20blat".
Not knowing anything about suPHP, I might as well agree with you. Maybe
switching to suPHP was not the only thing my provider has changed. So I
have no way of knowing what causes the trouble all of a sudden. At least
it wasn't me ;)
> For example, we host a user who uses WordPress, and he uses this
> feature. He has no problems, and we use suPHP.
>
> Bottom line: you need to work this out with your hosting provider, or
> pick one who offers what it is you need.
There are other ways of creating SEF URLs and I will try one of those.
Thank you, Jeremy and Max, for taking the time to shed some light on the
matter and for being so quick about it.
Later
Christian
Gruß
Christian Scholz-Flöter
--
ScholzBindestrichFlöter
Web-Dienstleistungen mit & ohne Spielkram
Lindenallee 46
20259 Hamburg
T: 040 411 617 78
F: 040 411 617 75
H: 0176 631 60 656
W: http://scholzbindestrichfloeter.de
E: cs at scholzbindestrichfloeter.de
More information about the suPHP
mailing list