示例
Prove Gin 1.12.0 gin.Context.ShouldBindJSON stream consumption behavior, Content-Type independence, empty-body EOF response, and error reporting without automatic response writes.
sha256:ddd9c90bd83fb9e4174328cb2f8943e90f9d44f955bffaa56ded31ee00924bf4
PUBLISHED
L3_CONTRACT_PASS
MIT-0
执行证据
分开显示声明环境和签名验证运行,明确样本的证明范围。
证据依据签名契约通过
验证回执1
验证级别L3_CONTRACT_PASS
声明的环境
- 执行上下文
- go
- 操作系统
- linux
- 架构
- x64
- 运行时
- go
- 语言
- go
- 包管理器
- go
验证运行环境
- 执行上下文
- go 1.26
- 操作系统
- linux alpine · musl
- 架构
- x64
- 运行时
- go 1.26
- 语言
- go
- 包管理器
- go
- 执行方式
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17
案例
- 目标
- Prove Gin 1.12.0 gin.Context.ShouldBindJSON stream consumption behavior, Content-Type independence, empty-body EOF response, and error reporting without automatic response writes. HOW
- 包
-
github.com/gin-gonic/gin v1.12.0
- 环境
- go
- 创建时间
- 2026-08-17T22:55:40Z
常见的想当然
ShouldBindJSON caches the request body to allow multiple binds on the same context, and requires an application/json Content-Type header before parsing.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- ShouldBindJSON consumes the request body stream directly without caching, causing any subsequent ShouldBindJSON call on the same context to return io.EOF.
- ShouldBindJSON parses the request body as JSON regardless of the Content-Type header, succeeding even on text/plain or empty MIME types.
- ShouldBindJSON returns io.EOF immediately when the request body is empty.
- ShouldBindJSON returns decoding errors directly to the caller without writing any response status or body to the response writer.
文件
- NOTES.md
- contract_test.go
- csx.json
- go.mod
- go.sum
下载源代码构件 (tar.gz)
原始种子者
csx-seed
验证回执
- go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9