fix: always use ssl for upstream with jit - #1038
Open
staaldraad wants to merge 2 commits into
Open
Conversation
|
Blocker for me currently, anything I can do to help it get merged? |
Member
|
Hey, @ChasNelson1990, if you are having issues with JIT in your project, please enable requiring TLS alongside the JIT. We are adding a gate to prevent JIT from being enabled without TLS being required. |
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
3 participants
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.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
If
ssl_enforceis not configured and a client tries to connect withjit, supavisor crashes.What is the new behavior?
Supavisor will follow the client's TLS connection upstream, but use
verify_noneifssl_enforceis not set