NYPHP Wiki WAS:Making URLs Search Engine Friendly - Follow Up

Hans Zaunere zaunere at
Wed Jun 5 00:24:50 EDT 2002

Hey Ophir and others,

Sorry I'm so late in getting back to this, but it kind of got lost in
my email stack.  I've cut and pasted Ophir's great info to the wiki
(, as well as the follow-up messages, which
provide additional info.  It's still rough, but I hope people will work
with it and get it formatted and completed in more of an article

Hopefully this will spark the building of additional articles and
information with this wiki, which then will be integrated with forums
and mailing lists, building a knowledge base.  To keep the wiki sane,
we have a wiki master/editor, available for contact at
wikimaster at  Thank your Charles!

People interested in participating with this, should join the NYPHP
Development list, since we don't want to clutter other's mail boxes too

Thank you,

Hans Z.

--- ophir prusak <prutwo at> wrote:
> Hi All,
> I wanted to go over a few items as a follow up to my presentation
> last
> night (ok - I forgot to look at my notes :)
> 1. I don't know how I forgot to mention this, but one of the biggest
> disadvantages of the PATH_INFO method is that it does not work with
> cgi
> versions of PHP.
> As in the nature of yesterday's presentation - does anyone know what
> error you get and why it doesn't work with cgi versions of PHP ?
> 2. When making your URLs search engine friendly, there is an
> advantage
> of using URLs that looks like an .html file (and not just a path, as
> often done with the PATH_INFO method).
> In the future, if you should want to make any of your pages truly
> static,
> it makes life easier.
> For example, one of the pages on my web site was getting a lot of
> traffic,
> so instead of having it be created on the fly, I simply created a
> crontab
> entry that once a day grabbed the dynamic page and saved it to a
> static
> page. Something like this:
> wget -o static-version.html
> Just a side note - I no longer do it this way, but instead use a
> output
> caching object to get almost the same performance gain.
> 3. Someone asked how do I make ANY file in a directory be treated
> like
> a PHP file, regardless of filename (under apache of course). Add this
> line in your .htaccess file for the directory you want to use:
> ForceType application/x-httpd-php   (or whatever mime type you use
> for
> php)
> For more details see
> I've created an example at:
> (I'll leave it up to the reader to write the regex to remove the
> .html
> from the PATH_INFO so your last value won't have .html appended to it
> ;)
> Hope you all learned something.
> Ophir
> ----
> Ophir Prusak
> Internet developer 
> prutwo at | 

Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup

More information about the talk mailing list