Skip to content

docs: README in the shared Zentinel format - #5

Merged
raffaelschneider merged 1 commit into
mainfrom
docs/readme
Oct 21, 2026
Merged

raffaelschneider merged 1 commit into
mainfrom
docs/readme

Conversation

@raffaelschneider

Copy link
Copy Markdown
Contributor

Rewrites the README to the org-wide standard in zentinelproxy/design#2 (readme/STANDARD.md): the shared lockup header, flat badges in the brand colors, the standard section order and footer. Commands, config keys, features and links were checked against the code; the quick-start KDL passes zentinel test.

Corrections:
Corrected claims (checked end to end with zentinel 0.6.50 and the agent built from main):

  • URL rewriting does not rewrite the path; the result only goes upstream as an X-Original-Path header
  • JSON body operations, convert, clear and replace are computed and discarded; body matching only runs in that phase
  • Method override, status override and templates are not applied
  • Response-only rules never fire (response phase needs a matched request rule)
  • Header matcher key is matches, not pattern (the old key silently became a presence check)
  • Body matcher is body: {json: [...]}, response matcher keys are status_codes/content_types, not status/content_type
  • Header add overwrites like set; glob * also matches /; default path type is regex, default priority 50
  • --socket is unreleased (main only); release 0.4.0 is gRPC-only, so the quick start uses gRPC
  • Proxy KDL used unix-socket path= and had no filter; replaced with a validated agents/filters config
  • No licence badge: the repository has no LICENSE file

Corrected claims (checked end to end with zentinel 0.6.50 and the agent built from main):
- URL rewriting does not rewrite the path; the result only goes upstream as an X-Original-Path header
- JSON body operations, convert, clear and replace are computed and discarded; body matching only runs in that phase
- Method override, status override and templates are not applied
- Response-only rules never fire (response phase needs a matched request rule)
- Header matcher key is `matches`, not `pattern` (the old key silently became a presence check)
- Body matcher is `body: {json: [...]}`, response matcher keys are `status_codes`/`content_types`, not `status`/`content_type`
- Header `add` overwrites like `set`; glob `*` also matches `/`; default path type is regex, default priority 50
- --socket is unreleased (main only); release 0.4.0 is gRPC-only, so the quick start uses gRPC
- Proxy KDL used `unix-socket path=` and had no filter; replaced with a validated agents/filters config
- No licence badge: the repository has no LICENSE file
@raffaelschneider
raffaelschneider merged commit 49f7f61 into main Oct 21, 2026
3 checks passed
@raffaelschneider
raffaelschneider deleted the docs/readme branch October 21, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant