blocks|key|166408|text|不是的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166409|内容类型应该是已知的任何类型，如果您知道的话。application/octet-stream在RFC2046中被定义为“任意二进制数据”，并且在这里有一个明确的重叠，它适用于其唯一目的是保存到磁盘的实体，并且从这一点上来说，它是任何"webby“之外的东西。或者从另一个角度来看它；使用application/octet-stream唯一可以安全地做的事情就是将它保存到文件中，并希望其他人知道它的用途。|offset|length|style|CODE|166410|您可以将Content-Disposition与其他内容类型(如image/png甚至text/html+)结合使用，以表明您想要保存而不是显示。在使用text/html的情况下，一些浏览器通常会忽略它，但我认为这是很久以前的事情了(我马上就要睡觉了，所以现在不打算开始测试一大堆浏览器；也许以后再测试)。|166411|RFC2616还提到了扩展令牌的可能性，现在大多数浏览器都认可inline，这意味着如果可能的话，你确实想要显示实体(也就是说，如果它是一种浏览器知道如何显示的类型，否则它在这个问题上别无选择)。这当然是默认行为，但这意味着您可以包括头文件的filename部分，如果用户尝试保存，浏览器可能会使用该部分(可能会进行一些调整，以便文件扩展名与相关内容类型的本地系统规范匹配，也可能不会)。|166412|因此：|166413|Content-Type:+application/octet-stream
Content-Disposition:+attachment;+filename="picture.png"|code-block|syntax|javascript|166414|意思是“我不知道这是什么鬼东西。请将它保存为一个文件，最好命名为picture.png”。|166415|Content-Type:+image/png
Content-Disposition:+attachment;+filename="picture.png"|166416|表示“这是一张PNG图片，请保存为文件，最好命名为picture.png”。|166417|Content-Type:+image/png
Content-Disposition:+inline;+filename="picture.png"|166418|意思是“这是一个PNG图片。除非你不知道如何显示PNG图片，否则请显示它。否则，或者如果用户选择保存它，我们建议将其命名为picture.png”。|166419|在那些识别inline的浏览器中，一些人会一直使用它，而另一些人会使用它，如果用户选择了“链接另存为”，但如果他们在查看时选择了“保存”(或者至少IE过去是这样的，几年前可能已经改变了)。|166420|entityMap^0|0|N|O|0|4|J|W|9|17|9|24|9|0|V|6|3D|8|0|0|0|0|0|0|0|0|5|6|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1A|8|@$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]|$D|1F|E|1G|F|G]|$D|1H|E|1I|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1J|8|@$D|1K|E|1L|F|G]|$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1O|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1P|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|U|3|V|5|P|7|1R|8|@]|9|@]|A|$Q|R]]|$1|W|3|X|5|6|7|1S|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|P|7|1T|8|@]|9|@]|A|$Q|R]]|$1|10|3|11|5|6|7|1U|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1V|8|@$D|1W|E|1X|F|G]]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|15|$]]

No.

The content-type should be whatever it is known to be, if you know it. <code>application/octet-stream</code> is defined as "arbitrary binary data" in RFC 2046, and there's a definite overlap here of it being appropriate for entities whose sole intended purpose is to be saved to disk, and from that point on be outside of anything "webby". Or to look at it from another direction; the only thing one can safely do with application/octet-stream is to save it to file and hope someone else knows what it's for.

You can combine the use of <code>Content-Disposition</code> with other content-types, such as <code>image/png</code> or even <code>text/html</code> to indicate you want saving rather than display. It used to be the case that some browsers would ignore it in the case of <code>text/html</code> but I think this was some long time ago at this point (and I'm going to bed soon so I'm not going to start testing a whole bunch of browsers right now; maybe later).

RFC 2616 also mentions the possibility of extension tokens, and these days most browsers recognise <code>inline</code> to mean you do want the entity displayed if possible (that is, if it's a type the browser knows how to display, otherwise it's got no choice in the matter). This is of course the default behaviour anyway, but it means that you can include the <code>filename</code> part of the header, which browsers will use (perhaps with some adjustment so file-extensions match local system norms for the content-type in question, perhaps not) as the suggestion if the user tries to save.

Hence:

<pre><code>Content-Type: application/octet-stream
Content-Disposition: attachment; filename="picture.png"
</code></pre>

Means "I don't know what the hell this is. Please save it as a file, preferably named picture.png".

<pre><code>Content-Type: image/png
Content-Disposition: attachment; filename="picture.png"
</code></pre>

Means "This is a PNG image. Please save it as a file, preferably named picture.png".

<pre><code>Content-Type: image/png
Content-Disposition: inline; filename="picture.png"
</code></pre>

Means "This is a PNG image. Please display it unless you don't know how to display PNG images. Otherwise, or if the user chooses to save it, we recommend the name picture.png for the file you save it as".

Of those browsers that recognise <code>inline</code> some would always use it, while others would use it if the user had selected "save link as" but not if they'd selected "save" while viewing (or at least IE used to be like that, it may have changed some years ago).

The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html">HTTP standard</a> says:

<blockquote>
 If this header [Content-Disposition: attachment] 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.
</blockquote>

I read that as

<pre><code>Content-Type: application/octet-stream
Content-Disposition: attachment
</code></pre>

But I would have thought that <code>Content-Type</code> would be <code>application/pdf</code>, <code>image/png</code>, etc.

Should I have <code>Content-Type: application/octet-stream</code> if I want browsers to download the file?

Do I need Content-Type: application/octet-stream for file download?

说：如果此头Content-Disposition: attachment用于应用程序/八位字节流content-type的响应中，则暗示的建议是用户代理不应显示响应，而是直接输入“将响应保存为...”对话框。我把它理解为Content-Type: application/octet-streamContent-Dis...

问下载文件是否需要Content-Type: application/octet-stream？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问下载文件是否需要Content-Type: application/octet-stream？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问下载文件是否需要Content-Type: application/octet-stream？
EN