From d9deb21eac1ad27dabacff18578d7dbaf124f55b Mon Sep 17 00:00:00 2001 From: Sheddy Date: Fri, 31 Oct 2025 08:22:04 +0000 Subject: [PATCH] Fix broken links in TCP Service and HTTP Router documentation --- .../reference/routing-configuration/http/routing/router.md | 2 +- docs/content/reference/routing-configuration/tcp/service.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/reference/routing-configuration/http/routing/router.md b/docs/content/reference/routing-configuration/http/routing/router.md index fa8ccb701..da515f937 100644 --- a/docs/content/reference/routing-configuration/http/routing/router.md +++ b/docs/content/reference/routing-configuration/http/routing/router.md @@ -110,7 +110,7 @@ labels: | `tls.options` | The name of the TLS options to use for configuring TLS parameters (cipher suites, min/max TLS version, client authentication, etc.). See [TLS Options](../tls/tls-options.md) for detailed configuration. | `default` | No | | `tls.domains` | List of domains and Subject Alternative Names (SANs) for explicit certificate domain specification. When using ACME certificate resolvers, domains are automatically extracted from router rules, making this option optional. | | No | | `observability` | Observability configuration for the router. Allows fine-grained control over access logs, metrics, and tracing per router. See [Observability](./observability.md) for details. | Inherited from entry points | No | -| `parentRefs` | References to parent router names for multi-layer routing. When specified, this router becomes a child router that processes requests after parent routers have applied their middlewares. See [Multi-Layer Routing](../../../../routing/multi-layer-routing.md) for details. | | No | +| `parentRefs` | References to parent router names for multi-layer routing. When specified, this router becomes a child router that processes requests after parent routers have applied their middlewares. See [Multi-Layer Routing](../routing/multi-layer-routing.md) for details. | | No | | `service` | The name of the service that will handle the matched requests. Services can be load balancer services, weighted round robin, mirroring, or failover services. See [Service](../load-balancing/service.md) for details. | | Yes | ## Router Naming diff --git a/docs/content/reference/routing-configuration/tcp/service.md b/docs/content/reference/routing-configuration/tcp/service.md index 348d83d9a..e719ddf42 100644 --- a/docs/content/reference/routing-configuration/tcp/service.md +++ b/docs/content/reference/routing-configuration/tcp/service.md @@ -165,7 +165,7 @@ In addition, if the parent of this service also has HealthCheck enabled, this se If HealthCheck is enabled for a given service and any of its descendants does not have it enabled, the creation of the service will fail. - HealthCheck on Weighted services can be defined currently only with the [File provider](../../../install-configuration/providers/others/file.md). + HealthCheck on Weighted services can be defined currently only with the [File provider](../../install-configuration/providers/others/file.md). ```yaml tab="Structured (YAML)" ## Dynamic configuration