Okay, then I'll remove the line for the next version, it won't touch
content-type.
[EMAIL PROTECTED] (Dan McCormick) wrote:
>It looks like Apache will follow its normal extension-to-MIME-type
>mapping, which seems like the right to do. I just tested it on a .ps
>file (using Apache::SSI to incl
It looks like Apache will follow its normal extension-to-MIME-type
mapping, which seems like the right to do. I just tested it on a .ps
file (using Apache::SSI to include something), and it sent it to me as
application/postscript.
Dan
Ken Williams wrote:
>
> [EMAIL PROTECTED] (Dan McCormick) w
> "KW" == Ken Williams <[EMAIL PROTECTED]> writes:
KW> I'll remove it if it won't break anything - will Apache set the type to
KW> text/html if no other information is given?
Apache has a default document type parameter, and I believe the
shipped configurations say text/plain.
Ken Williams wrote:
>
> [EMAIL PROTECTED] (Dan McCormick) wrote:
> >Hi,
> >
> >I was just trying to hack a script into showing its HTML output to a
> >browser by setting the content type to 'text/plain', but it looks like
> >Apache::SSI, which I'm using, always sets the content type to
> >'text/h
[EMAIL PROTECTED] (Dan McCormick) wrote:
>Hi,
>
>I was just trying to hack a script into showing its HTML output to a
>browser by setting the content type to 'text/plain', but it looks like
>Apache::SSI, which I'm using, always sets the content type to
>'text/html' (line 23 Apache::SSI).
I'll rem
