Sample
Show that `AuthenticityToken` defaults to global scope and is route-agnostic unless path and method are provided.
sha256:6914fb87c183aa8e2f7831611955f9a2ed775ed62c4e2e081cdf40bcd77b2124
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that `AuthenticityToken` defaults to global scope and is route-agnostic unless path and method are provided. HOW
- Packages
- rack-protection 4.2.1 rack-session 2.1.2 rack 3.2.7
- Environment
- ruby
- Created
- 2026-08-17T02:44:55Z
Commonly assumed
Developers should expect `Rack::Protection::AuthenticityToken.token(session)` to produce a route-specific token by default.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Leaving `path` and `method` unspecified when calling `Rack::Protection::AuthenticityToken.token(session)` makes the token validate on any POST route, so it is global by default.
- assert repeated calls to `Rack::Protection::AuthenticityToken.token(session)` return different masked values for the same session, proving masking randomness and not a static raw token cache.
- assert a path-scoped token generated with `path` and `method` is rejected on a different path.
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9