- From: Michael A. Puls II <shadow2531@gmail.com>
- Date: Thu, 22 Jul 2010 09:04:45 -0400
On Thu, 22 Jul 2010 09:00:09 -0400, Philip J?genstedt <philipj at opera.com> wrote: > On Thu, 22 Jul 2010 14:18:38 +0200, johan <johan at qx.se> wrote: >> If my web server can't handle mapping from a specific file to mime >> type, I can always deal with that through server side scripting, and >> instead of providing direct access to "video1.ogg" I'd go through >> "video.php?1" and set the headers myself. If I screw up, either through >> server side scripting or due to not configuring the web server >> correctly, or by choosing a web server that does not provide the >> functionality I need, I do not see that as the fault of browser >> developers. However, I do find it annoying to have to add a header like >> "x-content-type-options: nosniff" to force certain browsers to respect >> my choice of mime type. > > I hadn't heard of X-Content-Type-Options before, that certainly looks > crazy. I have: Header set X-Content-Type-Options "nosniff" in my .htaccess file. It's to tell IE not to do weird sniffing. -- Michael
Received on Thursday, 22 July 2010 06:04:45 UTC