Repository navigation
feat(haproxy): add optional User-Agent policy - #67
Merged
Merged
Conversation
fionera
marked this pull request as ready for review
July 11, 2026 02:45
The example was written on top of stacked branches that did not all merge: drop the pseudonymous source-log key and the inline POW worker bufsize tuning, and use the split berghain_challenge SPOE engine that master's berghain.cfg now defines.
fionera
force-pushed
the
agent/ua-policy-example
branch
from
July 11, 2026 03:02
f604e7a to
8ed9317
Compare
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
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.
What
Why
User-Agent strings are spoofable, so this is explicitly an operator-reviewed traffic-shaping example rather than authentication. It also fixes the omnibus config where mixed
curl + GPTBotmarkers could bypass the challenge.Closes #19.
Validation
npm run build