You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ChatGPT agent browses with a plain browser User-Agent and identifies
itself only via the Web Bot Auth Signature-Agent header, so the UA
token matcher cannot see it. Add a signature-agent block-list checked
in middleware as a second channel; the robots.txt-allowed OpenAI
fetchers (ChatGPT-User, OAI-SearchBot) keep winning via a UA override.
Matching the unverified header without validating the RFC 9421
signature is sound for a block-list: forging it only gets a request
blocked.
Also add UA tokens atlassian-bot (training) and google-agent (agent)
to tokens.ts and robots.txt, and extract the shared 403 into
policyResponse(). Middleware-level tests pin the header wiring in both
directions.
0 commit comments