Sample
Resolve default proxy, header, and SSL options when arguments are left unset or falsy in Faraday
sha256:092ddffa6f6f68434f6c75e4aaeb452e110f6dcb95be414f245e60a383cac209
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Resolve default proxy, header, and SSL options when arguments are left unset or falsy in Faraday HOW
- Packages
- faraday 2.14.3
- Environment
- ruby
- Created
- 2026-08-17T02:37:49Z
Commonly assumed
Leaving the proxy option unset in Faraday defaults to a direct connection with nil proxy options, and passing proxy false disables environment proxy discovery.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert leaving proxy unset automatically resolves to Faraday::ProxyOptions from the environment rather than nil
- assert passing proxy false does not disable environment proxy lookup and still resolves to ProxyOptions
- assert passing an empty hash for proxy successfully disables environment proxy resolution with an empty ProxyOptions
- assert leaving headers unset populates default User-Agent header rather than empty headers
- assert passing custom headers merges with default headers rather than replacing User-Agent
- assert leaving ssl verify unset returns nil for verify attribute but true for verify? predicate
- assert passing ssl verify as nil leaves verify? enabled and only explicit false sets disable? to true
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/client.rb
- 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