On Thu, Mar 27, 2008 at 04:42:33PM +0100, martin f krafft wrote: > Package: iceweasel > Version: 2.0.0.12-2 > Severity: normal > > http://www.ietf.org/rfc/rfc2183.txt says: > "The Content-Disposition response-header field has been proposed > as a means for the origin server to suggest a default filename if > the user requests that the content is saved to a file." >
It also says 2.2 The Attachment Disposition Type Bodyparts can be designated `attachment' to indicate that they are separate from the main body of the mail message, and that their display should not be automatic, but contingent upon some further action of the user. The MUA might instead present the user of a bitmap terminal with an iconic representation of the attachments, or, on character terminals, with a list of attachments from which the user could select for viewing or storage. > If I try to view > http://google-summer-of-code.googlecode.com/files/soc08-824x824_white.jpg, > Iceweasel forces me to download the file. This is wrong. It should > only use the header to suggest a filename *if* I chose to download. livehttpheaders tells me Content-disposition is attachment; filename=... QED. BTW, the RFC is about MUAs, not browsers ; RFC 2616 is the relevant one, but is not really verbose, though it kind of implies the save as dialog should show up if content-type is application/octet-stream. OTOH, it doesn't say anything about other cases. It also says "Content-Disposition is not part of the HTTP standard, but since it is widely implemented" All that to say I'm not really convinced this is a bug. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
