Set custom user agent string for hstspreload #121
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
lgarron
approved these changes
Jan 31, 2022
Co-authored-by: Lucas Garron <code@garron.net>
Co-authored-by: Lucas Garron <code@garron.net>
|
By the way, I know at least Mozilla was doing their own liveness checks — have you perchance talked to other browser vendors about using the same UA? |
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.
To stop hstspreload from being blocked by CDN and others' user agent filtering (#107), this CL changes the UA string from go's default string to
hsts-preload-bot. I tested this on a branch for several updates and we have confirmation that some folk were able to allowlist this UA string to avoid the issue with the live queries being blocked.