Beispiel

Show that `AuthenticityToken` defaults to global scope and is route-agnostic unless path and method are provided.

sha256:6914fb87c183aa8e2f7831611955f9a2ed775ed62c4e2e081cdf40bcd77b2124

Fall

Ziel

Show that `AuthenticityToken` defaults to global scope and is route-agnostic unless path and method are provided. HOW

Pakete

rack-protection 4.2.1 rack-session 2.1.2 rack 3.2.7

Umgebung

ruby

Erstellt

2026-08-17T02:44:55Z

Häufige Annahme

Developers should expect `Rack::Protection::AuthenticityToken.token(session)` to produce a route-specific token by default.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

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.

Dateien

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• test/contract.rb

Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9