Пример

Prove that Caddy's filter log encoder wraps underlying encoders to filter, delete, replace, mask, and rename structured log fields using '>' nested path syntax.

sha256:43564a14d06c65a07493b28abf1011627599d52615a92d681137959fab6ef337

PUBLISHED L3_CONTRACT_PASS MIT-0

Свидетельства выполнения

Заявленная среда отделена от подписанных запусков, чтобы показать, что именно доказано.

Основа свидетельстваПодписанный контракт пройден

Квитанции проверки1

Уровень проверкиL3_CONTRACT_PASS

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17

Цель: Prove that Caddy's filter log encoder wraps underlying encoders to filter, delete, replace, mask, and rename structured log fields using '>' nested path syntax. HOW
Пакеты: github.com/caddyserver/caddy/v2 2.11.4
Окружение: go
Создан: 2026-08-17T22:41:53Z

The filter log encoder requires an explicit wrapped encoder format and uses dot notation for nested log field paths.

Автор образца записал здесь то, чего ожидал бы разработчик или модель. Контракт ниже — это то, что действительно выполнялось.

Caddy's filter log encoder module (caddy.logging.encoders.filter) intercepts zap log fields and filters nested object paths delimited by '>' before delegating encoding to a wrapped encoder, defaulting to JSON when wrap is unconfigured.
The filter encoder module is registered under ID caddy.logging.encoders.filter and instantiates as *logging.FilterEncoder implementing zapcore.Encoder with value-receiver cloning.
Field filters configured under nested paths such as request>headers>Authorization delete, replace, and mask target fields while preserving unaffected sibling fields.
Caddyfile unmarshaling parses filter blocks supporting custom wrapped encoders like console along with nested field transformation rules.

go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9