Finally figured this one out, and I'm embarrassed to say that it was the browser caching the result.  *blush*

Thanks for your help,


Wouter van Vliet wrote:
On dinsdag 13 juli 2004 18:12, Colin JN Breame wrote:

Geoffrey Young wrote:

Colin JN Breame wrote:


I have a problem with apache and mod_perl;

The cgi-bin directory has many perl files in it.  All execute except which produces the browser Save As dialog.  The content of
the file saved is the content of (not something else).

However, if I rename the file to something other than (e.g., it executes as it should.

this definitely sounds like a mod_autoindex issue

I've removed any DirectoryIndex directives.


 Options +ExecCGI -Indexes

or just

 Options ExecCGI

don't forget to restart apache so the configuration changes are
applied :) 

if that doesn't work, I'm out of ideas, save issuing a direct telnet
request to your server to see what is actually coming off the wire. 
something like this should do the trick: 

$ telnet 80
Connected to (
Escape character is '^]'.
GET / HTTP/1.1

the last two lines are the ones you type, followed by two newlines.




Thanks for your response.

I've checked the Indexes option (Options +ExecCGI -Indexes) but it
seems to have no effect.

I've also removed all reference to mod_autoindex and again, the
problem persists.


Do you explicitly send an apropriate header? Though, .. This really doesn't
matter much when the unparsed file is send back to the client. Weird .. Can
you give us some (preferrably all) insight in the httpd.conf sections
referring to any perl parsing? (basically any line referring to perl, and
it's enclosing tags.

Silly thing maybe, but have you checked the file permissions on the file?