Sample
Prove that explicit Content-Type overrides can disable Faraday's request JSON encoder.
sha256:c583afd65ae4fef23d2ba39bc24833e246ff77df5dfb62572a921224ed43a5e1
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that explicit Content-Type overrides can disable Faraday's request JSON encoder. HOW
- Packages
- faraday 2.14.3
- Environment
- ruby
- Created
- 2026-08-17T02:38:02Z
Commonly assumed
If request middleware includes :json, Faraday always JSON-serializes Hash bodies, even when a different Content-Type header is supplied.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert that with request :json and no Content-Type override, a POST with {name: "sam"} serializes env.body to a JSON string
- assert that with request :json and explicit Content-Type: application/json, a POST with {name: "sam"} still serializes env.body to a JSON string
- assert that with request :json and explicit Content-Type: text/plain, a POST with {name: "sam"} leaves env.body as a Hash instead of serializing it to JSON
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9