Why would a web-data provider want to put html files in the cgi-bin directory? And/or why would a browser user find it more attractive to use a url like "www.hostname.xxx/cgi-bin/somepage.html", as opposed to something like "www.hostname.xxx/somepurpose/somepage.html" or just "www.hostname.xxx/sompage.html"?
On a unix-based web server, wouldn't a cgi-bin/foo.html file need to be flagged (chmod) executable? And/or would the web-server's config file need some tweak that enables *.html files to be treated as executable code? I don't doubt that the technique shown here is working for you, but I wonder if there might be some "issues" you haven't discussed that others might trip over.
In reply to Re: Perl header to serve up a .HTML file from a CGI directory
by graff
in thread Perl header to serve up a .HTML file from a CGI directory
by GrandFather
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |