-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does this work? #3
Comments
Alright, I just read through RFC 5245 - The Transport Layer Security (TLS) Protocol - Version 1.2 and RFC 7230 - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing which outline the structure of TLS and HTTP, and therefore explain why this works. It boils down to two facts, the first byte of a TLS message is always Here is the breakdown of why, with references: TLS
HTTP
|
Nice writeup! This might be good material for a 'How it works' section of the Readme. |
Hey @mscdex
I'm interested in using this library to provide automatic redirection from http -> https (see elastic/kibana#5959) but we're concerned about the magic here.
Would you be able to support this implementation with some information about how/why this works?
We are concerned about unintended side effects of serving both http and https traffic via the same port. Do you know of any caveats? Know of any supporting reference info?
Thank you so much for your help and this really neat (and surprisingly simple) library!
The text was updated successfully, but these errors were encountered: