localhost being redirected to https

[drKnoxy]

Do you want to request a feature or report a bug?
bug

What is the current behavior?

1. Open Chrome
2. Run yarn serve click on the link to the https server.
3. Stop the server
4. Run yarn dev
5. You can't access the http server because you keep getting upgraded to https

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Not sure, i had to empty cache and reload the page per these instructions
https://stackoverflow.com/questions/25277457/google-chrome-redirecting-localhost-to-https

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information.

• node version
• npm version
• Operating system: OSX

[developit]

I don't think there's anything we can do about this, it's just how redirects are cached.

[reznord]

I don't think there's anything we can do about this, it's just how redirects are cached

can we check for the service-worker while running preact watch and if it is present, we can un-register the SW and delete it).

What do you think @lukeed @developit ?

[osdevisnot]

My 2 cents. Although we can not fix it since this is how SW caching works. We can help users if use different ports for dev vs serve commands. For Example: yarn dev starts dev server on http://localhost:1234 and yarn serve starts prod served on https://localhost:8080. If interested, I can present the changes in PR.

[ForsakenHarmony]

serve is gone in next anyways