UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393

Steps to reproduce the problem:
1. use codebase https://github.com/boyofgreen/xboxMediaApp/tree/forDemo (forDemo branch
2. map IIS server to folder and start server
3. unregister and stop service worker for local host
4. comment out the sw registration on index.html
5. run page in chrome
6. turn off IIS server then refresh page (should not load)
7. turn IIS server back on and then uncomment the SW registration in index.html
8. refresh page and see SW take install
9. turn off IIS server again and refresh page
10. page errors out on connection instead of loading from cache

What is the expected behavior?
NOTE: this works fine with a node.js server, only fails on IIS.
expected to see the page refresh from the SW pulling content from cache API rather than failing to load.

What went wrong?
SW got a connection error instead of running.

Did this work before? Yes chrome 53

Does this work in other browsers? N/A

Chrome version: 51.0.2704.79  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

I compared headers to what comes from node, so I added cache-control: max-age=3600 header to IIS and it seemed to work