JCR-4536: Feature/enable insecure https host #88
Closed
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
…nvalid certs like curl
…https-host * feature/fix-build-issues: update java docs comments JCR-4492: Update Jackrabbit trunk to Oak 1.18.0 [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release jackrabbit-2.19.5 JCR-4467: Remove all usage of java.security.acl.Group for Java 14 (javadoc cleanup)
add missing override
update override call
This was referenced Nov 11, 2019
Member
|
I don't see a related JIRA ticket. @wildone Can you create one? |
wildone
changed the title
wildone
changed the title
Author
|
@kwin is there anything else needed? |
Member
Author
|
thank @kwin do you want me to add logging to prompt the user that insecure option being used? Any preference what the message for prompt should be? |
This was referenced Jul 3, 2020
Member
|
Obsoleted by #92. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Adding support for insecure parameter to allow access to https with invalid certs.
Enabling optional support for expired ssl certs when using https on development server with self generated certificates.