(...)

Hm. The downloaded "script" just contains the the ErrorDocument (500 Internal Server Error). It is not displayed because it's Content-type reads application/x-perl. I guess it's a bug (or a config issue?) in apache - it serves an error page with the wrong header. It should set Content-type: text/html when serving an error document.

What is the content in your case?

<update>

Well, just in case... seems to be a mod_mime issue. It seems that even for error documents served instead of failed cgi output, the mime type is set according to the cgi file extension (brr!). This might help:

• Sniff the traffic with e.g. wireshark (formerly ethereal) and look what apache sends as Content-type in the response header.
• Search for the directive TypesConfig in your apache configuration files.
• In the file that is configured under this term, search for the mime type apache sent in the header
• comment out that line
• change the DefaultType in your apache config to text/html (or text/plain)

</update>

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}