Menu
Mar 2, 2018 - use_course() fails with zip files on the Open Science Framework, but. Use_course() does not accept a ZIP with mime type 'application/octet-stream' #304. #does not work use_course('#works.
Hello all, All of a sudden on eBay everytime I go to a list of items page - but not the individual item itself - I get a pop-up that says plug-in needed 'application/octet stream' and leads me to a page full of plug-ins that is pretty much incomprehensible to me. I thought an octet stream was something that applied to PC/Windows things. It happens on all the computers, so it can't just be the one. Anyone have any idea what's going on?
Have I missed something? Is eBay quitting support for Macs? T'aint all bad, though; it makes it so cumbersome to use eBay I'm sure to save money. And thanks for your response. The problem struck all four computers last night about 1 A.M., some with Flash, and some with Shockwave plug-ins. (The plug-in that says Shockwave Flash is apparently just Flash) All the Macs have enough memory to choke a horse, including that assigned to IE.
(you'd think 100,000 K would be enough) Further investigation this morning reveals that iCab struggles with the whole eBay site - which it didn't used to do, but finally displays everything except the flashy (NPI) headers and without asking for more plug-ins. Haven't tried to download WamCOM and attempt that yet.
But - most interesting - mule #2, an old desktop I keep around for testing weird stuff, went right to the pages and displayed them properly, without problem. Turns out - at least so far - that as long as I go to eBay as a guest, and delete cookies that recognise me, eBay displays properly, without asking me for plug-ins.
Curiouser and curiouser!! I suspect eBay is just trying to wring more and more information out of its customers.and will finally get too greedy and destroy a good thing. But then, what do I know. Thanks again.Jon. Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.
Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.
Application/octet-stream is not a neutral content-type. When used in the Content-Type header of an http response, it may trigger download (and possibly execution). On top of being an unwanted behavior in most cases, this is a security issue. In case of serving files uploaded by users, It may allow them to makes visitors download virus and malwares without them knowing it (depending on the browser/download manager, the download could be hardly noticeable). Some OS/browser combination may also execute it or propose to execute it.
Also, assuming a file (or directory) is a binary file just because it has an unknwon extension is totally wrong and an unexpected behavior. The expected and optimal behavior is to return null when the content type could not be guessed. We've discussed a bit on the subject here. In a standard point of view, here the rules:.
which defines only known types The 'octet-stream' subtype is used to indicate that a body contains arbitrary binary data. which tell what to do when the type is unknown A sender that generates a message containing a payload body SHOULD generate a Content-Type header field in that message unless the intended media type of the enclosed representation is unknown to the sender. If a Content-Type header field is not present, the recipient MAY either assume a media type of 'application/octet-stream' (RFC2046, Section 4.5.1) or examine the data to determine its type. So unknown type = no Content-Type header.