Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat(s2n-tls-hyper): Allow plain HTTP connections #4978
feat(s2n-tls-hyper): Allow plain HTTP connections #4978
Changes from 2 commits
00f3218
3f13019
9c998c6
9f217b9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thought: is
insecure
too strong a word for this? Maybe something likewith_plaintext_http
would be a bit more ambivalent.Although I guess if you're going through the trouble of using the
s2n-tls-hyper
connector, plaintext http is a little sus. I don't think the current naming was bad, just curious about reasoning.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah
insecure
was meant less as a warning and more to differentiate from "secure" in HTTPS. Sowith_plaintext_http
works just as well if that makes the meaning more clear.