configuring apache to automatically send Content-Type header and exec as CGI based on file extension

princepawn has asked for the wisdom of the Perl Monks concerning the following question:

I would label this off-topic, but given the large number upvotes I have received recently, it is only fitting that I catch a couple of right hooks to the jaw to spice things up.

Anyway, how do I set up Apache so that it executes files with a .sgi extension as CGI scripts and so that Apache automatically sends the Content-type: text/html header?

Edit: chipmunk 2001-11-03

Comment on configuring apache to automatically send Content-Type header and exec as CGI based on file extension Select or Download Code

Replies are listed 'Best First'.
Re: configuring apache to automatically send Content-Type header and exec as CGI based on file extension by blakem (Monsignor) on Nov 03, 2001 at 14:08 UTC
(assuming you meant '.cgi' not '.sgi') In your httpd.conf: `AddHandler cgi-script .cgi AddType text/html .cgi DefaultType text/html` [download] -Blake	[reply] [d/l]
(jeffa) Re: configuring apache to automatically send Content-Type header and exec as CGI based on file extension by jeffa (Bishop) on Nov 03, 2001 at 21:20 UTC
Slightly OT, i just wanted to add the fun to be had with 'CGI extensions': .jpg, .png, .gif in conjunction with GD .xls in conjunction with Spreadsheet::WriteExcel I used the second one to allow IE users to get their database results in the form of an Excel Spreadsheet. By configuring Apache to accept .xls as a CGI script (in one particular directory), the not-so-skilled users could save the file without having to change the name of the file from say, foo.cgi to foo.xls - which would have confused them. The first one can be called just like a regular image: `<img src="foo.png">`. Fun stuff! jeffa	[reply] [d/l]
Re: configuring apache to automatically send Content-Type header and exec as CGI based on file extension by Zecho (Hermit) on Nov 03, 2001 at 18:12 UTC
Look for commonhttpd.conf first. Some versions use that file instead.	[reply]


Problems? Is your data what you think it is?
	PerlMonks