|
|
Posted by John Dunlop on 10/28/06 09:08
Andy Dingley:
[...]
> If you want to "recommend" saving rather than display, then send a
> content-type that's likely to do this for most browsers. As you don't
> say what your content is, then it's hard to recommend one (although
> application/octet-stream might do the trick).
RFC2616 : 19.5.1 says:
| If [Content-Disposition] is used in a response with the
| application/octet-stream content-type, the implied
| suggestion is that the user agent should not display
| the response, but directly enter a `save response
| as...' dialog.
http://www.ietf.org/rfc/rfc2616.txt
Not only do I find this paragraph odd and wholly unnecessary, coming
from (an appendix of) the HTTP spec, but I also regard
Content-Disposition (spit!) on the WWW as pernicious. Don't get me
wrong, I think Content-Disposition has its place - mail rather than the
WWW.
--
Jock
Navigation:
[Reply to this message]
|