This repository was archived by the owner on May 28, 2018. It is now read-only.
Allow the same Jersey client to be used for both authenticated and non-authenticated URLs #3563
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
agherardi
force-pushed
the
basicAuthenticator
branch
from
a268b0c to
fd4f6ac
Compare
Contributor
Author
Contributor
Author
|
Any updates? Thanks |
…n-authenticated resources
agherardi
force-pushed
the
basicAuthenticator
branch
from
fd4f6ac to
382ad4c
Compare
Contributor
Author
|
Any updates? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When registering the basic HttpAuthenticationFeature, the BasicAuthenticator shouldn't throw an exception when credentials are missing, as the request could be for a non-authenticated resource.
This allows the same Jersey client to be used for both authenticated and non-authenticated URLs.