RE: Re[2]: [cobalt-users] RAQ3: Problem parsing default 404 page

["Andy Brown" <andy.brown@xxxxxxxxxxxxx>]

<snip>
No, and Perl is working just fine.
The files are already in valid HTML syntax, and the embedded should
make no difference.

Could be, but even if I add the header for the browser to tell what
type of file it is by itself, it still displays the text in the file.

I suspect another header is added before the text is retrieved from
the fileNotFound.html file in /usr/admserv/.cobalt/error

Can anyone tell for certain whether this file is parsed by a Perl
script?

Any other suggestions why all browsers display the HTML file as if it
was a text file?
</snip>

If you take a look in /etc/httpd/conf/srm.conf you'll find the error folder is parsed by perl, using the Cobalt::HtmlLocale and this script is located at
/usr/lib/perl5/site_perl/5.005/Cobalt/HtmlLocale.pm
So would be worth running that through the perl syntax highlighter and see if any errors are thrown out (perl -c -w HtmlLocale.pm)

You are right in saying another header is added, since this is parsed by perl, it is the perl script which should be sending out the header.
If it is pushing out the script raw then its either apache not correctly processing the file, or its perl not sending back the correct http headers.
Do any perl scripts on your server work when they're parsed via apache?

If you've replaced the cobalt scripts with known working standard .html files and it still shows source, then drop into apache config and check the file extension association. Do .html files work fine on the server or just .htm ?

Regards,

Andy
andy@xxxxxxxxxx
http://www.raqpak.com/ <-- Raq/Qube unofficial PKGs and support advice