Sample
Measure a 303 redirect after Req 0.7.2 encodes a JSON POST using an offline adapter
sha256:57dca645282763e9d6f66858b3d74356c8d500fcc6a730e19b3187f45238fd43
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- elixir 1
- Operating system
- linux
- Architecture
- x64
- Runtime
- elixir 1
- Language
- elixir
- Package manager
- mix
Verification-run environments
- Execution context
- elixir 1
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- elixir 1
- Language
- elixir
- Package manager
- mix
- Execution
- container · docker
CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-17
Case
- Goal
- Measure a 303 redirect after Req 0.7.2 encodes a JSON POST using an offline adapter HOW
- Packages
-
req 0.7.2
- Environment
- elixir 1
- Created
- 2026-08-17T04:46:35Z
Commonly assumed
Following a 303 after a JSON POST keeps the POST method, encoded body, and content-type on the redirected request.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert the offline adapter first receives POST /start whose body iodata becomes the exact JSON bytes and whose content-type is application/json
- assert the adapter's 303 Location response triggers a second offline request to /final as GET with nil body and no content-type
- assert Req.request! returns the second adapter response with status 200 and body ok
Files
- NOTES.md
- csx.json
- mix.exs
- mix.lock
- test/contract_test.exs
- test/test_helper.exs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- elixir 1 · linux alpine/x64 · docker · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-17 · ed25519:d91480838ac982c9