Re:Changes to SameSite Cookie Behavior – A Call to Action fo...
by VWWHFSfQ on Wednesday August 05, 2020 @07:27AM
(#24059567)
This is so annoying. Our app requires HTTPS when not in debug mode. If you run the app locally and accidentally forget to turn on debugging then it will try to redirect to HTTPS. Firefox sees this and then from then on tries to force HTTPS, even after you've restarted the app with debugging. And now you simply can't access the non-HTTPS local site and I have no idea how to make Firefox forget about the HTTPS redirect. Infuriating.
Re:Changes to SameSite Cookie Behavior – A Call to Action fo...
by danielhlockard on Wednesday August 05, 2020 @08:08AM
(#24059910)
Clear it from your HSTS cache, I bet you're setting that in the app when https is hit.
Re:Changes to SameSite Cookie Behavior – A Call to Action fo...
by VWWHFSfQ on Thursday August 06, 2020 @06:46AM
(#24069760)
It's not HSTS. I've tried multiple methods to clear localhost from Firefox HSTS cache and it's not in there. But it still forces the HTTPS redirect.
Re:Changes to SameSite Cookie Behavior – A Call to Action fo...
by iggldiggl on Thursday August 06, 2020 @08:58AM
(#24070467)
301 cache then?
Re:Changes to SameSite Cookie Behavior – A Call to Action fo...
by marksomnian on Wednesday August 05, 2020 @07:47AM
(#24059744)
With Chrome you can go to chrome://flags, find “unsafely treat insecure origins as secure”, and allowlist your dev server.
Re:Changes to SameSite Cookie Behavior – A Call to Action fo...
by joewrong on Wednesday August 05, 2020 @07:53AM
(#24059800)
This may help https://github.com/FiloSottile/mkcert
There’s any number of circumstances in which my development machines don’t have HTTPS.