You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes when I go to glycam.org is resolves correctly to the https version. Other times not. Having a hard time nailing down when and why this happens. I've seen this behavior in both firefox and brave browsers. I'm fairly sure this is a recent (last few weeks or months at most) development as I haven't encountered this before last week. Clearing my cookies seemed to trigger it happening once I got it to stop.
The text was updated successfully, but these errors were encountered:
I suspect there is caching or some such in your browser. I never see this - or very rarely see it and can't remember it right now. I usually have the opposite trouble with the browser trying to force https with sites that don't have it.
But, we can probably add a fix on our end.
@thecoulter - That 404 is coming from Traefik, as you probably know. I suspect there is a way to force redirection of http requests to https at the Traefik level. That way, even if a browser requests the insecure version, it will be switched to an https connection.
That ticket is about using 'www' in the url. Apparently, that was fixed
This is (probably) happening because Traefik is not handling entrypoints on port 80. The config I'm looking at only handles 443, but I'm not sure I'm looking at the most current one.
@thecoulter - I think the issue is that Traefik needs to be told to listen on / acknowledge port 80 but then redirect to https (443). The config I'm looking at seems to only listen o 443. But, it's been a while. I am pretty sure this is a Traefik thing.
High priority if others can reproduce this behavior.
See my jam session here with comments:
https://jam.dev/c/d335208b-2712-4e50-8b55-3cb700257ffe
Sometimes when I go to glycam.org is resolves correctly to the https version. Other times not. Having a hard time nailing down when and why this happens. I've seen this behavior in both firefox and brave browsers. I'm fairly sure this is a recent (last few weeks or months at most) development as I haven't encountered this before last week. Clearing my cookies seemed to trigger it happening once I got it to stop.
The text was updated successfully, but these errors were encountered: