Process Different File Types with PHP in IIS7

A slight follow on from an earlier post I made about custom error pages in IIS7, I needed to get IIS to process JavaScript files in PHP. This is really useful if you need to do some pre-processing before the JS hits the browser. In order to get this to work I added the following to the Web.config file in the root of the site:

Note that I am using PHP in FastCGI mode.

Also, make sure you set scriptProcessor to the path of your php-cgi.exe. The other thing I had to do, as Chrome was reporting a Resource interpreted as Script but transferred with MIME type text/html warning when the JavaScript file was loaded, was to add header("Content-type: text/javascript; charset: UTF-8"); to the js file.

One thing you can do to speed things up is specify a specific file in the path parameter of the Web.config. For example to only process my_js_file.js use path="my_js_file.js". And of course, you can add Web.config files in sub-folders so only certain files types are processed with PHP in those folders.

Configure IIS7 for Custom Error Pages

I've recently (and finally!) moved to Windows 7 and with it IIS 7. I got PHP installed (using FastCGI) all fine, but was having major issues getting my custom 404 handlers to work with PHP. I found loads of articles all over the web that directed me in the right direction. But no one single article worked for me so this is what worked for me...

All the following settings can be done via the IIS Manager (Control Panel > Administrative Tools), but for me, I created the following Web.config file and put that in the root of the site that I wanted the 404 handler to be working on.

Note the use of errorMode="Custom" and existingResponse="Replace". Hope this works out for you :)

woff 404 Font Not Found

I noticed recently that a site I work on that uses a woff font was getting a 404 not found error in Chrome. It was also giving a Resource interpreted as Font but transferred with MIME type application/octet-stream. I spent ages hunting around the forums and found no solution to it.

The fact that I was getting a 404 was the oddest thing and made me think that IIS wasn't serving the font correctly (it was being used by the browser none the less). So I went about checking to see what .woff MIME type was set in IIS. The local computer had no MIME Type handling for .woff so I added it (Right-click > Properties > MIME Types... Extension: .woff and Type: application/x-font-woff). That didn't fix it :(

I right-clicked the Default Web Site > Properties > HTTP Headers > MIME Types... and added the new extension there also (Extension: .woff and Type: application/x-font-woff). Reloaded the page and the warning and error had gone - happy days!

Update...
Thanks to the comment below added by RyanonRails, here is an example web.config (http://pastie.org/4081017):

<system.webServer>
    <httpErrors errorMode="Detailed" />
    <staticContent>
      <mimeMap fileExtension=".coffee" mimeType="coffeescript" />
      <mimeMap fileExtension=".woff" mimeType="application/x-font-woff" />
    </staticContent>
  </system.webServer>
</configuration>