- From: Robert Burns <rob@robburns.com>
- Date: Tue, 28 Aug 2007 19:00:13 -0500
- To: "Philip Taylor (Webmaster)" <P.Taylor@Rhul.Ac.Uk>
- Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, public-html@w3.org
Hi Phil, On Aug 28, 2007, at 7:31 AM, Philip Taylor (Webmaster) wrote: > > Boris Zbarsky wrote: >> <http://issues.apache.org/bugzilla/show_bug.cgi?id=14095#c9> >> That comment says that IIS defaults to a type. It doesn't say >> that there is no way to turn off the defaulting. I don't know >> whether there is; if someone with easy access to IIS could check, >> that would be great. > > I have easy access to IIS 6, running under Windows Server 2003; > if you can outline what you would like tested, I will be more > than happy so to do and report back. I can also make the test > site publicly accessible so that others can verify my tests. Basically we're looking to figure out whether IIS can be configured to sent no content-type header at all. In particular, it would be worthwhile to determine what IIS sends by default when no filename extension can be determined — though I believe IIS also uses sniffing by default. So it would be best to place a file on the server that IIS had no way of sniffing and no way to determine the filename extension mapping. Whatever information you can provide for us on this would be great. 1) what does IIS do in its default configuration when it cannot determine a file's type? 2) is there any way to change the configuration to send no content- type header at all when it cannot determine a file's type? 3) how is it configured by default to send content-type headers for files with no filename extension? 4) can one configure it to send a particular content-type header for files with no filename extension? There is a wiki page on this, so you could add the results of these questions somewhere there (or reply here). <http://esw.w3.org/topic/HTML/ContentTypeIssues> Take care, Rob
Received on Wednesday, 29 August 2007 00:01:35 UTC