mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-26 02:47:15 +00:00
zeekay
4e83ffa927
- CRD API group: traefik.io -> hanzo.ai (GroupName, apiVersion, RBAC)
- Docker/provider label prefix: traefik.* -> ingress.* (all providers)
- CRD kind: TraefikService -> IngressService
- Directory renames: traefikio/ -> hanzoai/ (types, generated code, listers, informers, clientset)
- Config root name: traefik -> ingress (KV stores, file paths, env prefix)
- Metrics prefix: traefik_ -> ingress_
- Kubernetes annotations: traefik.ingress.kubernetes.io/ -> ingress.kubernetes.io/
- Gateway annotations: traefik.io/ -> hanzo.ai/
- Internal provider package: provider/traefik -> provider/builtins
- Type renames: TraefikLog -> IngressLog, TraefikCmdConfiguration -> IngressCmdConfiguration
- Generated client methods: TraefikV1alpha1() -> HanzoV1alpha1(), Traefik() -> Hanzo()
- Sample configs: traefik.sample.{toml,yml} -> ingress.sample.{toml,yml}
- Config paths: /etc/traefik/ -> /etc/ingress/, ~/.config/traefik -> ~/.config/ingress
- Default cert CN: TRAEFIK DEFAULT CERT -> INGRESS DEFAULT CERT
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:
- "traefik.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.
- "traefik.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 |