Serviceworker conflict with HTTP basic auth? : <p>I'm trying to protect a site during an early stage of development from casual prying eyes. Basic auth over HTTPS seemed like a reasonable solution but the presence of a serviceworker seems to prevent it from working in Chrome.  This happens specifically if a serviceworker is already installed, but the browser does not have an active authorisation for the desired realm.</p>

<p>Chrome shows that the response was a 401 in the network timeline</p>

<p><a href="https://i.stack.imgur.com/WUole.png" rel="noreferrer"><img src="https://i.stack.imgur.com/WUole.png" alt="401 in Network timeline"></a></p>

<p>And also shows that the browser tab is receiving the right response headers:</p>

<pre><code>HTTP/1.1 401 Unauthorized
WWW-Authenticate: Basic realm="My realm"
Date: Tue, 21 Jun 2016 03:09:35 GMT
Connection: close
Cache-Control: no-cache
</code></pre>

<p>But it does not prompt for a login, it just shows the content body of the 401 response.</p>

<p>Is this a Chrome bug, or is it likely to be a problem with my ServiceWorker?</p>
