DOCS: Agent signature element specification - #22
Merged
Conversation
jwrosewell
force-pushed
the
feature/agent-signature-element
branch
2 times, most recently
from
September 2, 2026 03:30
1802f80 to
91ac1cb
Compare
jwrosewell
force-pushed
the
feature/agent-signature-element
branch
from
September 2, 2026 03:35
91ac1cb to
9e33d24
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.
Adds the behaviour contract for the agent signature element that
51Degrees/pipeline-dotnet#373 implements. The element checks the
request signature an automated agent sends under the IETF Web Bot
Auth protocol and reports whether the signature verified, with an
absent signature never reading as evidence against a request.
The page follows the shape of
set-headers-element.mdand keeps tothe contract rather than the .NET API: the evidence the element asks
for, the thirteen step status and reason decision order (five
statuses, seventeen reason codes), the key directory cache semantics
including the wait budget, the Timeout outcome and the
stale-while-refreshing rule with its one further lifetime bound, the
fetch safety rules (HTTPS only, no user information, private and
loopback addresses refused, redirects refused, response bytes
capped), the twelve properties, and the configuration options with
their defaults and validation.
The .NET implementation in pipeline-dotnet#373 is the reference for
the other language ports, and every behaviour stated on the page was
checked against that code rather than written from memory. The one
part of the contract that depends on other repositories is the web
evidence for
@method,@path,@queryand@target-uri, which51Degrees/pipeline-dotnet#374 tracks, and the page says those read
Unverified with ComponentUnavailable until the evidence exists.