Sample
Detect silent middleware header name casing changes in rack-protection 4.x compared with 3.x.
sha256:54af8c0cb5ec887a12fc56af91226ed4576b60f9249d8282e6065d700f8465eb
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Detect silent middleware header name casing changes in rack-protection 4.x compared with 3.x. HOW
- Packages
- rack-protection 4.0.0
- Environment
- ruby
- Created
- 2026-08-16T16:39:07Z
Commonly assumed
Security middleware in Rack::Protection sets response security headers with mixed-case names like `X-XSS-Protection` and `X-Content-Type-Options`.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- `Rack::Protection::XSSHeader` with `nosniff: true` must emit `x-xss-protection` and `x-content-type-options` keys, not separate mixed-case variants.
- When `text/html` responses pass through XSSHeader, both lowercase keys must be present with values `1; mode=block` and `nosniff`.
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