Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re: mod_rewrite VS SSI VS your better idea

by rnewsham (Curate)
on Aug 20, 2013 at 05:14 UTC ( #1050123=note: print w/replies, xml ) Need Help??


in reply to mod_rewrite VS SSI VS your better idea

There are various options, the simplest if it is available to you is reconfigure the server so you can run cgi scripts from the public directory. So you can just do www.mysite.com/home.cgi. Although I would recommend using mod rewrite to allow that to be accessed as www.mysite.com/home which is tidier, preferred by search engines and allows you to change the script type without updating links and creating redirects. For example you could change home.cgi to .html, .shtml, .pl, .fcgi or switch to using Dancer and all your links to www.mysite.com/home can remain unchanged.

If the scripts must be kept in the cgi-bin then I would recommend using mod rewrite. You don't need a .htaccess file for each script you can use a single set of rules. Something like one of the two examples below should work. The first should allow you to use www.mysite.com/home.cgi and the second www.mysite.com/home. These are just basic examples you would need to build upon these to do exactly what you want and protect against unwanted rewrites.

RewriteEngine On RewriteCond %{REQUEST_URI} /*.cgi$ RewriteRule (.*) ../cgi-bin/$1 [l] or RewriteEngine On RewriteCond %{SCRIPT_FILENAME} !-f RewriteCond %{SCRIPT_FILENAME} !-d RewriteRule (.*) ../cgi-bin/$1.cgi [l]

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1050123]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (2)
As of 2020-12-06 01:46 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How often do you use taint mode?





    Results (65 votes). Check out past polls.

    Notices?