State that the Workbench port is HTTPS only - #56
Merged
Conversation
Reaching the published Workbench port over plain http gets no reply at all — the Chronicle port multiplexes HTTP/1.1 and HTTP/2 through ALPN, which requires TLS — so name the requirement and the symptom where the URL is printed and documented.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changed
cratis runnow states that the Chronicle Workbench is HTTPS only when it prints the URL, and the documentation names the empty-response symptom (ERR_EMPTY_RESPONSE,curl: (52) Empty reply from server) you get from reaching it ashttp://. The Chronicle port multiplexes HTTP/1.1 and HTTP/2 through ALPN, which requires TLS, so it has no plaintext mode.