Adding config driven support for sslOnly #8
Conversation
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
|
Why is this still open can this be merged and be deployed, this feature would be very helpful |
|
Thanks |
|
This is very helpful, why its not merged? |
|
I don't think they are intending to merge this due to conflict of interest. |
|
What's the conflict of interest? |
|
Hello all, just wanted to update you. We are in the middle of trying to get 1.17.0 out the door and we are in a code freeze at the moment. We have been talking about this one internally and intend to address the desire, either by merging this as is or allowing you to disable ssl in another way. Thank you |
|
Any movement on this? Still very much a desired feature. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
To fix #2
Simply allowing the end user to override sslOnly option