Skip to content

docs: explain upstream x402 cache header limitation #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nkavian merged 1 commit into from
Oct 8, 2026
Merged

docs: explain upstream x402 cache header limitation #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -949,6 +949,13 @@ response with a payment failure. Avoid irreversible business side effects in a
handler without your own reconciliation design. InFlow does not roll back the
handler's work.

The upstream x402 Python 2.25.0 cache helper can mistake `private` inside a quoted
extension value such as `example="a, private, b"` for a real directive. A receipt
response can therefore lack the intended private cache policy. This is tracked in
[upstream issue #3747](https://github.com/x402-foundation/x402/issues/3747).
Explicitly include an unqualified `private` directive in `Cache-Control` on affected
handler responses. InFlow does not replace the upstream cache parser.

The clients are framework-independent and do not import FastAPI. Use them with
other upstream asynchronous adapters where appropriate. For anonymous external
on-chain facilitation, explicitly use
Expand Down
Loading