Recent searches
Search options
Administered by:
@develwithoutacause@techhub.socialHow have we not solved #WiFi redirects yet? If you're activating a new modem or accessing a public network, you just get a bunch of #SSL errors as the network tries to redirect you but the browser refuses them. Users don't understand what these errors mean and definitely don't know the neverssl.com trick.
Is there really no way we can securely say: "The router is refusing your connection and redirecting you to your ISP's website"? This feels solvable, isn't it?
@develwithoutacause There’s a proposal for a dedicated HTTP status code: https://httpwg.org/specs/rfc6585.html#using-511.
`HTTP/1.1 511 Network Authentication Required`
@tomayac Interesting! How would that work with HTTPS connections? Wouldn't the server fail the TCP handshake before the HTTP 511 is ever sent?
Displaying any #HTML content at all seems like a strange choice to me given the origin implications. I guess I would have expected the response to just contain a `Location` style redirect header which maybe requires the user to confirm via a user agent-displayed alert box.
Definitely glad to see there's some interest and movement here. I don't want to keep having to teach people about neverssl.com, and this seems like a path to fixing that. 
@develwithoutacause Sorry, I haven’t thought this through thoroughly myself, just remembered it exists. The authors who have thought this through are linked at the end: https://httpwg.org/specs/rfc6585.html#rfc.authors.