Beispiel

Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default middleware inclusion.

sha256:211d7395fda74de66490b727f70e99004de2ff33d235445d7c9a625f290745c2

Fall

Ziel

Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default middleware inclusion. HOW

Pakete

rack-protection 4.2.1

Umgebung

ruby

Erstellt

2026-08-16T16:38:09Z

Häufige Annahme

Initializing Rack::Protection with default options includes session hijacking defense that clears the session when a client user-agent header changes.

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

• Rack::Protection.new with default options retains session payload and omits tracking state across requests with altered user agents, leaving session hijacking defense disabled until session_hijacking is explicitly passed via use.
• Passing use: :session_hijacking to Rack::Protection.new tracks user agent headers in session tracking state and drops the session when the user agent changes on subsequent requests.

Dateien

• Gemfile
• 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-16 · ed25519:d91480838ac982c9