Sample
Detect that missing session state in AuthenticityToken is an exception path instead of a normal 403 defense path.
sha256:4807cc2d2429689bda2de67ed180fc5ac55fea621ceae46855551facba968089
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Detect that missing session state in AuthenticityToken is an exception path instead of a normal 403 defense path. HOW
- Packages
- rack-protection 4.2.1
- Environment
- ruby
- Created
- 2026-08-16T16:33:47Z
Commonly assumed
If session setup is missing, `Rack::Protection::AuthenticityToken` should surface the `RuntimeError` from `Base#session` and stop request handling immediately.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert that `Rack::Protection::AuthenticityToken.new(app).call(Rack::MockRequest.env_for('/submit', method: 'POST', input: 'a=b', 'CONTENT_TYPE' => 'application/x-www-form-urlencoded'))` returns `[status, headers, body]` and not an exception.
- assert that the status from that tuple is exactly 403.
- assert that the body includes `Forbidden` because rejection is handled by `deny` even when session setup is wrong.
Files
- Gemfile
- 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-16 · ed25519:d91480838ac982c9