Beispiel

Enforce allowed Content-Type headers using chi middleware.AllowContentType without bypassing empty POST requests or rejecting GET requests with payloads

sha256:037510e85f8dba770d16f88ad5b0518221d158d0c8dd7458642d69b91926d5e1

Fall

Ziel

Enforce allowed Content-Type headers using chi middleware.AllowContentType without bypassing empty POST requests or rejecting GET requests with payloads HOW

Pakete

github.com/go-chi/chi/v5 v5.2.1

Umgebung

go

Erstellt

2026-08-17T01:26:39Z

Häufige Annahme

middleware.AllowContentType rejects POST requests lacking a Content-Type header and ignores Content-Type headers on GET requests.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• middleware.AllowContentType allows a body-less POST request with an empty Content-Type header through to the handler with HTTP 200 rather than rejecting it based on the HTTP method
• middleware.AllowContentType rejects a GET request carrying a body and an empty Content-Type header with HTTP 415 StatusUnsupportedMediaType rather than exempting GET requests from media type validation
• middleware.AllowContentType rejects a POST request with an explicit disallowed Content-Type header with HTTP 415 StatusUnsupportedMediaType and an empty 0-byte response body
• middleware.AllowContentType rejects a POST request with an invalid base media type with HTTP 415 StatusUnsupportedMediaType
• middleware.AllowContentType normalizes case and media type parameters like charset allowing uppercase APPLICATION/JSON with HTTP 200

Dateien

• NOTES.md
• allow_content_type_test.go
• csx.json
• go.mod
• go.sum

Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9