Do not advertise HTTP caches #1915
Open
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
|
I'm not sure this is the best approach here. Are these caches really HTTP-only? Seems like we only need to avoid redirecting to HTTP but we don't need to remove all the caches that speak both protocols. For example, the LIGO cache at Caltech has both https://stashcache.ligo.caltech.edu:8443 and http://stashcache.ligo.caltech.edu:8000; not redirecting for HTTP will have minimal impact but removing support for HTTPS will have a huge impact at their site. |
jhiemstrawisc
requested changes
Jan 18, 2025
turetske
force-pushed
the
no-redirectects-http-caches
branch
from
41aadb2 to
3b41c4f
Compare
turetske
force-pushed
the
no-redirectects-http-caches
branch
from
3b41c4f to
5455562
Compare
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.
For security reasons, we want to stop advertisement of HTTP caches.
This only occurs with non-pelican caches, which should be phased out by April. As such this shouldn't cause a large disruption (there are only a few caches where this occurs)
I decided to stop those caches from advertising to the director because I don't want them to be listed in the federation if they aren't available to the user.