示例
Verify whether request methods with custom casing keep their exact method token through Guzzle dispatch.
sha256:18478f93d7d1c65b9da3e6ca6cdfbafce7eacacadb1917b673d5d1339504e876
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Verify whether request methods with custom casing keep their exact method token through Guzzle dispatch. HOW
- 包
- guzzlehttp/guzzle 8.0.2
- 环境
- php
- 创建时间
- 2026-08-17T02:35:07Z
常见的想当然
A developer expects Guzzle to normalize request methods to uppercase before dispatch, so 'gEt' will become 'GET'.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- assert GuzzleHttp\Client::request sends the exact method token 'gEt' without uppercasing it to 'GET'
文件
- NOTES.md
- composer.json
- composer.lock
- csx.json
- test/contract.php
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- php 8 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · composer@1 · 2026-08-17 · ed25519:d91480838ac982c9