Sample
Rack::Protection::HostAuthorization does not reject single-label Host headers
sha256:3d8ac15f35f3c3e019faf9ccb83c6c2034edb9e5b9579ec2ec19f966b685d17b
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Rack::Protection::HostAuthorization does not reject single-label Host headers HOW
- Packages
- rack-protection 4.2.1
- Environment
- ruby
- Created
- 2026-08-17T02:45:21Z
Commonly assumed
Rack::Protection::HostAuthorization rejects requests with a bare single-label Host header
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- A direct Rack::Protection::HostAuthorization middleware returns status 200 for a bare single-label Host header when no permitted_hosts restriction is configured.
Files
- Gemfile
- Gemfile.lock
- 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