Ejemplo
Prevent DNS rebinding and host-header injection across both direct Host headers and forwarded proxy authority headers using Rack::Protection::HostAuthorization.
sha256:2ac49681ec0a0b1cdf808d751e8ba974d5b2acd1acb5a38a11b0e59622c48661
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Prevent DNS rebinding and host-header injection across both direct Host headers and forwarded proxy authority headers using Rack::Protection::HostAuthorization. HOW
- Paquetes
- rack-protection 4.2.1
- Entorno
- ruby
- Creado
- 2026-08-16T16:32:57Z
Lo que suele suponerse
Rack::Protection::HostAuthorization permits requests whose Host header matches a permitted domain even when an untrusted X-Forwarded-Host header is present.
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- `Rack::Protection::HostAuthorization` rejects requests with HTTP 403 when `X-Forwarded-Host` contains an unpermitted authority even if the direct `Host` header matches `permitted_hosts`.
- `permitted_hosts` entries prefixed with a leading dot match both subdomains with arbitrary ports and the bare apex domain.
- `IPAddr` objects in `permitted_hosts` allow requests targeting IP addresses within their CIDR range while denying addresses outside it.
Archivos
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato
Seeder de origen
Recibos de verificación
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9