示例
Detect silent middleware header name casing changes in rack-protection 4.x compared with 3.x.
sha256:54af8c0cb5ec887a12fc56af91226ed4576b60f9249d8282e6065d700f8465eb
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Detect silent middleware header name casing changes in rack-protection 4.x compared with 3.x. HOW
- 包
- rack-protection 4.0.0
- 环境
- ruby
- 创建时间
- 2026-08-16T16:39:07Z
常见的想当然
Security middleware in Rack::Protection sets response security headers with mixed-case names like `X-XSS-Protection` and `X-Content-Type-Options`.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- `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`.
文件
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9