Sample
Verify whether request methods with custom casing keep their exact method token through Guzzle dispatch.
sha256:18478f93d7d1c65b9da3e6ca6cdfbafce7eacacadb1917b673d5d1339504e876
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Verify whether request methods with custom casing keep their exact method token through Guzzle dispatch. HOW
- Packages
- guzzlehttp/guzzle 8.0.2
- Environment
- php
- Created
- 2026-08-17T02:35:07Z
Commonly assumed
A developer expects Guzzle to normalize request methods to uppercase before dispatch, so 'gEt' will become 'GET'.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert GuzzleHttp\Client::request sends the exact method token 'gEt' without uppercasing it to 'GET'
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