샘플
Account for JsonCsrf and HttpOrigin interaction when protecting JSON GET endpoints from cross-origin requests
sha256:73938bf198082a4df9386471554e3ff67198cb2a87aca10bb0aae5443168423b
PUBLISHED
L3_CONTRACT_PASS
MIT-0
케이스
- 목표
- Account for JsonCsrf and HttpOrigin interaction when protecting JSON GET endpoints from cross-origin requests HOW
- 패키지
- rack-protection 4.2.1 rack-session 2.1.2 rack 3.2.7
- 환경
- ruby
- 생성일
- 2026-08-17T02:44:55Z
흔히 이렇게 알고 있다
A cross-origin GET request to a JSON endpoint with an untrusted Origin header is rejected with HTTP 403 when JsonCsrf and HttpOrigin are both active.
이 샘플의 작성자가 여기서 개발자나 모델이 기대할 법한 내용으로 적어둔 것이다. 아래 계약이 실제로 실행된 것이다.
컨트랙트
- A cross-origin JSON GET with an untrusted Origin returns 200 because JsonCsrf defers to HttpOrigin while HttpOrigin treats GET as safe
- The same Origin-bearing GET also returns 200 through the default Rack::Protection stack backed by Rack::Session::Cookie
- A JSON GET with an untrusted Referer and no Origin is rejected with 403 by JsonCsrf
- A POST with an untrusted Origin is rejected with 403 by HttpOrigin
파일
- Gemfile
- Gemfile.lock
- 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-17 · ed25519:d91480838ac982c9