Sample
Distinguish a null per-request header value from clearing all inherited headers in Guzzle 7.9.0.
sha256:e99720d321ab01e65d4356739c5384c92a7bd703593fa53533187be0adfde72a
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Distinguish a null per-request header value from clearing all inherited headers in Guzzle 7.9.0. HOW
- Packages
- guzzlehttp/guzzle 7.9.0
- Environment
- php
- Created
- 2026-08-17T02:34:56Z
Commonly assumed
A null value for one per-request header removes that inherited header exactly like setting the entire headers option to null.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Passing headers with a null value sends the request and overrides that inherited header with an empty value while preserving other defaults.
- Passing the entire headers option as null clears all inherited client headers before dispatch.
Files
- NOTES.md
- composer.json
- composer.lock
- csx.json
- test/contract.php
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- php 8 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · composer@1 · 2026-08-17 · ed25519:d91480838ac982c9