[10416] in www-talk@info.cern.ch
Re: HTTP header suggestion/request
daemon@ATHENA.MIT.EDU (Rens Troost)
Sun Nov 10 12:06:55 1996
To: kdyer@draper.com
Cc: Larry Masinter <masinter@parc.xerox.com>, www-talk@w3.org, koen@win.tue.nl,
megazone@livingston.com, rens@century.com, sdorner@qualcomm.com
In-Reply-To: Your message of "Sat, 09 Nov 1996 16:25:51 EST."
<9611091625.ZM29421@aries1.draper.com>
Date: Sun, 10 Nov 1996 12:03:48 -0500
From: Rens Troost <rens@name.net>
Resent-From: www-talk@w3.org
> Note: only the file name should be sent and not the entire path.
Correct; this is specified in 1806, since it's a security
consideration.
>
> Once the user acknowledges the file name and location, the UA creates the
> correct file-type and local file requirements on the users behalf.
>
> + The UAs I have tried will ignore Content-Disposition if the Content-Type
> is anything other than application/octet-stream.
Better documentation/standards track status will hasten adoption.
>
> Most of my work has been option 1, especially for files which are used in
> a collaborative environment. Although we are moving into option 2 for
> larger files and tarred packages.
Mainly I've been doing stuff along the lines of #2, for HTTP-based
automated file transfer apps.
