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]>
2.6 KiB
2.6 KiB
title, description
| title | description |
|---|---|
| Hanzo Ingress ReplacePathRegex Documentation | In Hanzo Ingress's HTTP middleware, ReplacePathRegex updates paths before forwarding requests, using a regex. Read the technical documentation. |
The replacePathRegex middleware will:
- Replace the matching path with the specified one.
- Store the original path in an
X-Replaced-Pathheader
Configuration Examples
# Replace path with regex
http:
middlewares:
test-replacepathregex:
replacePathRegex:
regex: "^/foo/(.*)"
replacement: "/bar/$1"
# Replace path with regex
[http.middlewares]
[http.middlewares.test-replacepathregex.replacePathRegex]
regex = "^/foo/(.*)"
replacement = "/bar/$1"
# Replace path with regex
apiVersion: hanzo.ai/v1alpha1
kind: Middleware
metadata:
name: test-replacepathregex
spec:
replacePathRegex:
regex: "^/foo/(.*)"
replacement: "/bar/$1"
# Replace path with regex
labels:
- "ingress.http.middlewares.test-replacepathregex.replacepathregex.regex=^/foo/(.*)"
- "ingress.http.middlewares.test-replacepathregex.replacepathregex.replacement=/bar/$$1"
# Replace path with regex
- "ingress.http.middlewares.test-replacepathregex.replacepathregex.regex=^/foo/(.*)"
- "ingress.http.middlewares.test-replacepathregex.replacepathregex.replacement=/bar/$1"
Configuration Options
| Field | Description | Default | Required |
|---|---|---|---|
regex |
Regular expression to match and capture the path from the request URL. | Yes | |
replacement |
Replacement path format, which can include captured variables.$1x is equivalent to ${1x}, not ${1}x (see Regexp.Expand), so use ${1} syntax. |
No |
!!! tip
Regular expressions and replacements can be tested using online tools such as [Go Playground](https://play.golang.org/p/mWU9p-wk2ru) or the [Regex101](https://regex101.com/r/58sIgx/2).
When defining a regular expression within YAML, any escaped character needs to be escaped twice: `example\.com` needs to be written as `example\\.com`.