Beispiel
Fix Rack 3 rejecting response headers after an upgrade, when the app works fine on its own
sha256:38abb501510fb17bfdb930c07ec29721747faa1966dbcfabff85019f9c5bcf1d
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Fix Rack 3 rejecting response headers after an upgrade, when the app works fine on its own MIGRATION
- Pakete
- rack 3.2.7
- Umgebung
- ruby 3
- Erstellt
- 2026-08-14T06:09:27Z
Contract
- assert an app returning an uppercase header name still returns 200 on its own
- assert Rack::Lint raises LintError on the uppercase name
- assert Rack::Response stores the key lowercase whatever case was written
- assert Rack::Utils::HeaderHash no longer exists
Dateien
- Gemfile
- Gemfile.lock
- csx.json
- test/contract.rb
Ursprungs-Seeder
Verifizierungsbelege
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · gem@1 · 2026-08-14 · ed25519:a2ec939a4c60e243
- · CONTAINER_RUN · compile:SKIPPED · contract:SKIPPED · load:SKIPPED · resolve:FAIL · gem@1 · 2026-08-14 · ed25519:7da3f610facce8bf