> Bri Carey wrote:
>
> > > > When I display an .iphtml page in Netscape, everything seems to be fine.
> > > >
> > > > When I display it in IE (4.72), I get a plain text output of the source
> > > > code, including html tags.
> > > >
> > > > Why this discrepancy?
> >
> > I've tried setting the default type to text/html in the httpd.conf file and
> > that didn't seem to do the trick.
> >
> > I appreciate the input that I've received.
> >
> > I've also noticed that both browsers display the code, although they format
> > the html properly, when I try to execute the script inside of a standard
> > .html document. I know that's not the standard (embedded Perl should have
> > .iphtml extensions - at least that's the way it seems to be). Yes, I have
> > made the appropriate changes in the httpd.conf file:
> >
> > PerlModule Apache::ePerl
> > <Files ~ "/root/of/webmaster/area/.+\.html$">
> > Options +ExecCGI
> > SetHandler perl-script
> > PerlHandler Apache::ePerl
> > </Files>
> >
> > You can see this now at http://www.uncricket.com/index1.html
> >
> > Thanks again for any input.
> >
> > Regards,
> > Bri
even though cliff said:
>I don't think you are using the Files directive properly.
>Try something like this:
>
> <DirectoryMatch /root/of/webmaster/area/>
> <FilesMatch ".*\.html?$">
> SetHandler perl-script
> PerlHandler Apache::ePerl
> Options +ExecCGI
> </FilesMatch>
> </DirectoryMatch>
and he's probaly got something there--but if netscape is
getting eperl-processed html and explorer is getting the
source to the perl-bristled code, there's something very
odd going on there.
whether you use lynx or opera or icab, the browser should
get what the server sends out, and -- UNLESS you have
browser-specific settings somewhere -- they should ALL
receive the exact same stuff.
i.e. if you turn off eperl, then everyone will see the
perl that bristles throughout your html. if it's on
and working, then all browsers will get the resulting
html markup.
...unless you have some browser-specific gizmo happening,
which (if my fading gray cells are working) is possible
in apache.
[as a security measure, to hide the inner workings of our
website, we use .htaccess frequently to enable eperl here
and there while letting the user think everything is just
a plain old html file, as in:
# .htaccess settings file:
<Files {somePatternMaybe}.html>
SetHandler perl-script
PerlHandler Apache::ePerl
Options +ExecCGI
</Files>
hopefully this will make it more difficult for black-hatted
sniffers to know what's happening behind the scenes...
now if we could only get apache to not identify itself
in the "Server:" header...]
