On Jul 23, 2008, at 9:18 AM, Daniel Kinzler wrote:
2008/7/23 River Tarnell
<https://wiki.toolserver.org/view/Switchboard> to find out how.
The second way seems to rely on "AddHandler" for .php files. I
sometimes use rewrite rules to hide the ugly-looking file extension
completely, does the described .htaccess in public_html affect them?
If you want to rewrite Foo.php to Foo.phpf or Foo to Foo.phpf or
is up to you. The example of rewriting Foo.php to Foo.phpf is just
to show how
to let old URLs ending with .php remain functional. The important
bit is that
the actual file path (right side of the rewrite rule) is phpf.
Using AddHandler works fine if you want to do it for all files in a
that have a given extension, e.g. .php. I tried to apply it to a
full file name,
but that doesn't seem to work - it likes only file extensions, and
thus can not
be used for individual files. This is a bit silly, but apparently,
we have to
live with it :)
You should be able to limit to specific files by wrapping the
AddHandler directives in <Files> (or similar) elements.
at apache version because the Server header served by the toolserver
doesn't specify a version. Apache 1.3 equivalent doc: http://
See also: http://httpd.apache.org/docs/2.0/sections.html#file-and-web
Also, general note: I don't have a toolserver account so if there's
something specific to the toolserver I might be a little off.