Re:BugMeNot Is Gone
by zachflower on Tuesday November 15, 2022 @05:27PM
(#33616008)
Looks like it's just misconfigured. The non-https is still around: http://bugmenot.com
[ Parent
| on HN ]
Re:BugMeNot Is Gone
by titaniumtown on Tuesday November 15, 2022 @05:39PM
(#33616189)
that doesn't work either
Re:BugMeNot Is Gone
by misterbwong on Tuesday November 15, 2022 @05:34PM
(#33616100)
Looks like that's gone too
Not from here, no...
Re:BugMeNot Is Gone
by jbverschoor on Tuesday November 15, 2022 @05:45PM
(#33616256)
Hsts?
HTTP Strict Transport Security
It allows servers to specify that browsers should never even attempt to make an unencrypted request to the site and instead silently convert any such requests to encrypted requests.
This header is good for security but it’s also convenient for old sites that don’t want to update their existing links. They can upgrade the whole site to HTTPS without any content changes.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/St...
https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
Trying from another browser works
That stands for HTTP Strict Transport Security. Its a http header that basically tells your browser to only connect to this website via HTTPS/TLS for a configurable amount of time.
Its a protection mechanism that prevents encryption stripping man-in-the-middle attacks.
Re:BugMeNot Is Gone
by jbverschoor on Wednesday November 16, 2022 @03:37AM
(#33620455)
I know, that's why I mentioned it.
The http site worked fine for me, so I figured parent post already has a HSTS entry in his browser
Re:BugMeNot Is Gone
by AdamJacobMuller on Tuesday November 15, 2022 @05:48PM
(#33616291)
works fine for me