Marc Evans wrote:
>
> This is a function of the browser. A review of the HTTP standard
> reveals that there is currently no official standard (to my knowledge)
> for the server to inform the browser of the filename for a stream it
> sends.
The file naming isn't at issue, it's that the client is getting
something it's not prepared to handle.
This could either be because:
a) the script executed, but the content-type of its output isn't
recognised by the client, OR
b) the server isn't executing the script, but sending it verbatim.
The former seems more likely, since the latter would require the
server to differentiate its actions based on the client information.
Possibly, but not probable.
--
#ken P-)}
Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
