Sample
faraday 2.14.3: Prove that explicit Content-Type overrides can disable Faraday's request JSON encoder.
Verified sample for gem faraday 2.14.3: Prove that explicit Content-Type overrides can disable Faraday's request JSON encoder. The contract ran on ruby 3 …
sha256:c583afd65ae4fef23d2ba39bc24833e246ff77df5dfb62572a921224ed43a5e1
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
ruby linux x64 ruby ruby bundler
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-17 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-18 |
Case
HOW- Goal
- Prove that explicit Content-Type overrides can disable Faraday's request JSON encoder.
- Packages
- Symbols
-
- Faraday::Connection
- Faraday::Request::Json
- Environment
- ruby
- Created
- 2026-08-17T02:38:02Z
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