8 ms·

Looks like it's just misconfigured. The non-https is still around: http://bugmenot.com http://bugmenot.com

• misterbwong 4y ago
  Looks like that's gone too
  • antx 4y ago
    Not from here, no...
  • jbverschoor 4y ago
    Hsts?
    • deleted 4y ago
      [deleted]
    • ricardo81 4y ago
      https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security Trying from another browser works
    • deleted 4y ago
      [deleted]
    • lhoff 4y ago
      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.
      • jbverschoor 4y ago
        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
    • sholladay 4y ago
      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/Strict-Transport-Security https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/St...
  • AdamJacobMuller 4y ago
    works fine for me
  • sph 4y ago
    It's not, the HTTPS site has the HSTS header, so your browser will always redirect to the HTTPS version even if you try the plaintext port. Gotta clear your browser cache, or try another browser.
• titaniumtown 4y ago
  that doesn't work either