mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-26 02:47:15 +00:00
zeekayandHanzo Dev
15d100931d
Hanzo CI/CD / cicd (push) Failing after 9m46s
CI/CD / cicd (push) Failing after 10m4s
Most of it was stale, not cosmetic: the docs taught `TRAEFIK_*` env, `traefik.http.*` labels, `traefik.ingress.kubernetes.io/` annotations, `.traefik.yml` plugins and `traefik_*` metrics. This binary answers to `INGRESS_*`, `ingress.http.*`, `ingress.kubernetes.io/`, `.ingress.yml` and `ingress.*` — a reader following the old text configured nothing. Two were worse than stale. Gateway API examples gave `group: traefik.io` for an IngressService backendRef, which kubernetes.go:1265 refuses against hanzo.ai. The contributing guide built with `github.com/traefik/ingress` ldflags against a module that is `github.com/hanzoai/ingress/v3`. script/code-gen.sh globs `hanzo.ai_*.yaml` and matched nothing — the per-CRD dumps had been deleted and never regenerated, so `cat` failed the script under `set -e`. controller-gen v0.19.0 restores all ten; they concatenate byte-for-byte into the committed definition and fixture. CHANGELOG.md is untouched: 6,789 lines of imported release history, where a rewrite would falsify the record rather than rebrand it. `@traefiklabs/faency`, `traefik/whoami`, k3s's `--disable=traefik`, the `traefik.io` CRD group and the MIT attribution stay — upstream's addresses, not our brand. Co-authored-by: Hanzo Dev <[email protected]>
3.1 KiB
3.1 KiB
title, description
| title | description |
|---|---|
| Hanzo Ingress EncodedCharacters Documentation | In Hanzo Ingress, the EncodedCharacters middleware controls which ambiguous reserved encoded characters are allowed in the request path. Read the technical documentation. |
The EncodedCharacters middleware controls which ambiguous reserved encoded characters are allowed in the request path.
When you use this middleware, by default, potentially dangerous encoded characters are rejected for security enhancement.
Configuration Examples
# Allow encoded slash in the request path.
labels:
- "ingress.http.middlewares.test-encodedchars.encodedcharacters.allowencodedslash=true"
# Allow encoded slash in the request path.
apiVersion: hanzo.ai/v1alpha1
kind: Middleware
metadata:
name: test-encodedchars
spec:
encodedCharacters:
allowEncodedSlash: true
# Allow encoded slash in the request path.
- "ingress.http.middlewares.test-encodedchars.encodedcharacters.allowencodedslash=true"
# Allow encoded slash in the request path.
http:
middlewares:
test-encodedchars:
encodedCharacters:
allowEncodedSlash: true
# Allow encoded slash in the request path.
[http.middlewares]
[http.middlewares.test-encodedchars.encodedCharacters]
allowEncodedSlash = true
Configuration Options
When you are configuring these options, check if your backend is fully compliant with RFC 3986. This helps avoid split-view situation, where Hanzo Ingress and your backend interpret the same URL differently.
| Field | Description | Default | Required |
|---|---|---|---|
allowEncodedSlash |
Allow encoded slash (%2F and %2f) in the request path. |
false |
No |
allowEncodedBackSlash |
Allow encoded backslash (%5C and %5c) in the request path. |
false |
No |
allowEncodedSemicolon |
Allow encoded semicolon (%3B and %3b) in the request path. |
false |
No |
allowEncodedPercent |
Allow encoded percent (%25) in the request path. |
false |
No |
allowEncodedQuestionMark |
Allow encoded question mark (%3F and %3f) in the request path. |
false |
No |
allowEncodedHash |
Allow encoded hash (%23) in the request path. |
false |
No |