Re^3: perl hide by html....

Of course, once again, you will need to have that parsing configured on the webserver, but it's possible to either use only index pages, and refer to them as directories, so that the browser never sees the file extension

Wouldn't the index page need to be setup to be executable by file extension, though? Or do webservers usually have a configuration option to allow exection by filename rather than just extension?

Comment on Re^3: perl hide by html....

Replies are listed 'Best First'.
Re^4: perl hide by html.... by jhourcle (Prior) on May 02, 2005 at 21:08 UTC
If you're using mod_rewrite, you can set options on just about anything, but that's not quite what I was alluding to. For what I was talking about in that particular case, what you'd do is set your DirectoryIndex or equivalent in your web server, so that instead of referencing your pages as something like the following: http://server/path/page1.html http://server/path/page2.html http://server/path/page3.html You instead use: http://server/path/page1 http://server/path/page2 http://server/path/page3 Each one of those is actually a directory, so in the case of Apache, it's going to redirect you to: http://server/path/page1/ http://server/path/page2/ http://server/path/page3/ And in each of those directories, you'll have the appropriate file extension for whatever you're trying to trigger. (index.shtml, index.php, index.jsp, index.cfm, index.cgi, etc, which you've defined as being your directory index, and configured your server to handle the extension correctly)	[reply]

Replies are listed 'Best First'.

Re^4: perl hide by html....
by jhourcle (Prior) on May 02, 2005 at 21:08 UTC

If you're using mod_rewrite, you can set options on just about anything, but that's not quite what I was alluding to.

For what I was talking about in that particular case, what you'd do is set your DirectoryIndex or equivalent in your web server, so that instead of referencing your pages as something like the following:

http://server/path/page1.html
http://server/path/page2.html
http://server/path/page3.html

You instead use:

http://server/path/page1
http://server/path/page2
http://server/path/page3

Each one of those is actually a directory, so in the case of Apache, it's going to redirect you to:

http://server/path/page1/
http://server/path/page2/
http://server/path/page3/

And in each of those directories, you'll have the appropriate file extension for whatever you're trying to trigger. (index.shtml, index.php, index.jsp, index.cfm, index.cgi, etc, which you've defined as being your directory index, and configured your server to handle the extension correctly)

[reply]