Conditional 304 replay

Quirk · GET /api/x402/edge-conditional-304 · Edge / CDN Controls

The paid resource carries an ETag, and a later conditional request is answered 304 from cache without re-payment.

Explanation

The paid resource is served with an ETag, and a later conditional request (If-None-Match) is answered 304 Not Modified from cache without a fresh payment, letting a client replay access for free. The merchant must not let conditional revalidation bypass the payment gate on protected resources.

What to watch

The first paid call returns an ETag; a replay with -H 'If-None-Match: "paid-resource-v1"' (no payment) returns 304.

Facilitator

Settled against the live Radius testnet facilitator (https://facilitator.testnet.radiustech.xyz). A valid payment runs a real /verify and /settle on-chain.

Metadata

Back to catalog