patchwork: support configurable user agent - #436
Open
OllieinCanada wants to merge 2 commits into
Open
Conversation
added 2 commits
August 15, 2026 16:43
Some Patchwork instances may reject unidentified API clients. Allow each API policy to provide a User-Agent and send it on both lookup and check requests. Cover the transport behavior with a deterministic localhost test. Signed-off-by: Oliver Slapinski <olliefromcanada@gmail.com>
Signed-off-by: Oliver Slapinski <olliefromcanada@gmail.com>
OllieinCanada
marked this pull request as ready for review
August 15, 2026 20:51
Collaborator
|
Hi Ollie, could you please fix those commits? IOW - have the SOBs and authorship match the account in which you are submitting this PR with? I'll review once that happens :) |
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
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.
Fixes #282
Summary
Allow each Patchwork API policy to configure an identifiable HTTP
User-Agent.
Why
Some Patchwork deployments use automated-client protections and may reject
requests that do not identify a real service contact. Sashiko previously
provided no way to set that header, so operators could not follow an
instance's client-identification policy without changing the code.
Changes
No default identity is hard-coded; each deployment controls the value it
publishes.
Validation
and verifies their User-Agent and authorization headers
rejects the installed GCC 9.4 compiler; GitHub CI provides the authoritative
clippy and unit-test results