[XrdSecgsi] Make proxy cache path aware. #980
Merged
Conversation
This file contains 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
|
@simonmichal Looks good. I agree that using UsrProxy should do the job. And is only used there, so there is no risk of using different tags. I think you can go ahead and test it in the release candidate. |
|
Thanks, I cleaned up the PR and am merging it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This aims at fixing #976.
@gganis : I think we can simply use
UsrProxyas the tag used to query proxy cache. Alternatively, we could hash the proxy location and create a tag likeProxy: + hash(alternative version in the comments). Please let me know which one suits us better!Michal