feat(lb): url path routes

Author: RoRoJ

pages/load-balancer/concepts.mdx

@@ -173,7 +173,7 @@ See [balancing-methods](#balancing-methods).
 
 ## Routes
 
-Routes allow you to specify, for a given frontend, which of its backends it should direct traffic to. For [HTTP](#protocol) frontends/backends, routes are based on HTTP Host headers. For [TCP](#protocol) frontends/backends, they are based on **S**erver **N**ame **I**dentification (SNI). You can configure multiple routes on a single Load Balancer.
+Routes allow you to specify, for a given frontend, which of its backends it should direct traffic to. For [HTTP](#protocol) frontends/backends, routes are based on HTTP Host headers or URL paths. For [TCP](#protocol) frontends/backends, they are based on **S**erver **N**ame **I**dentification (SNI). You can configure multiple routes on a single Load Balancer.
 
 ## Object Storage failover
 

pages/load-balancer/faq.mdx

@@ -73,11 +73,11 @@ Yes, you can restrict the use of a `TCP` port or `HTTP` URL using ACLs. Find mor
 
 ## What is a route?
 
-Once you have created one or more Load Balancers, you can create routes. Routes indicate how to direct incoming connections to certain backends based on various parameters such as IP addresses, path, host, etc. You can choose the frontend to which the rule should apply, and the backend it should direct to. Routes can be based on **Server Name Indication** (SNI) for TCP Load Balancers, or the **HTTP Host header** for HTTP Load Balancers. Check out our [dedicated documentation](/load-balancer/how-to/create-manage-routes/) for more information.
+Once you have created one or more Load Balancers, you can create routes. Routes indicate how to direct incoming connections to certain backends based on various parameters such as IP addresses, path, host, etc. You can choose the frontend to which the rule should apply, and the backend it should direct to. Routes can be based on **Server Name Indication** (SNI) for TCP Load Balancers, or the **HTTP Host header** or **URL path** for HTTP Load Balancers. Check out our [dedicated documentation](/load-balancer/how-to/create-manage-routes/) for more information.
 
 ## Can I add multiple backends to a frontend?
 
-Yes, this is possible using routes. When you create a frontend, you must select a "default" backend, to which it forwards traffic when the request doesn't match any configured route. But via the **routes** tab for your frontend in the Scaleway console, you can create routes to different backends from the same frontend. Routes are currently supported based on the value of the `Host` header of incoming HTTP requests for HTTP backends, or on SNI for TCP backends.
+Yes, this is possible using routes. When you create a frontend, you must select a "default" backend, to which it forwards traffic when the request doesn't match any configured route. But via the **routes** tab for your frontend in the Scaleway console, you can create routes to different backends from the same frontend. Routes are currently supported based on the value of the `Host` header of incoming HTTP requests for HTTP backends, URL paths, or on SNI for TCP backends.
 
 ## What is a health check?
 

pages/load-balancer/how-to/create-manage-routes.mdx

@@ -9,7 +9,7 @@ dates:
 import Requirements from '@macros/iam/requirements.mdx'
 
 
-Routes allow you to specify, for a given frontend, which backends it should direct traffic to depending on the requested host. For [HTTP](/load-balancer/concepts/#protocol) frontends/backends, routes are based on HTTP Host headers. For [TCP](/load-balancer/concepts/#protocol) frontends/backends, they are based on **S**erver **N**ame **I**dentification (SNI). You can configure multiple routes on a single frontend. When no route rules match for an incoming connection/request, the frontend will forward to its default backend.
+Routes allow you to specify, for a given frontend, which backends it should direct traffic to depending on the requested host. For [HTTP](/load-balancer/concepts/#protocol) frontends/backends, routes are based on HTTP Host headers or URL paths. For [TCP](/load-balancer/concepts/#protocol) frontends/backends, they are based on **S**erver **N**ame **I**dentification (SNI). You can configure multiple routes on a single frontend. When no route rules match for an incoming connection/request, the frontend will forward to its default backend.
 
 <Requirements />
 
@@ -37,11 +37,12 @@ Routes allow you to specify, for a given frontend, which backends it should dire
 
     If you have selected an HTTP frontend/backend pair:
 
-    - **HTTP Host header**: Enter an HTTP Host header value to filter for (for example `www.example-domain.com`). Traffic with a matching value in its HTTP Host header will be directed to the specified target backend.
+    - **HTTP Host header**: Enter an HTTP Host header value to filter for (for example `example-domain.com`). Traffic with a matching value in its HTTP Host header will be directed to the specified target backend, OR
+    - **URL path**: Enter a URL path value to filter for (for example `/dashboard`)
 
     If you have selected a TCP frontend/backend pair:
 
-    - **SNI value**: Enter an SNI value to filter for (for example `www.example-domain.com`). Traffic with a matching SNI value will be directed to the specified target backend.
+    - **SNI value**: Enter an SNI value to filter for (for example `example-domain.com`). Traffic with a matching SNI value will be directed to the specified target backend.
 
 8. Choose whether to match all subdomains of the given SNI / Host header value, by checking the relevant box. This will ensure that all requests to subdomains of the value (e.g. `blog.example-domain.com`) also use this route.
 

pages/load-balancer/reference-content/configuring-frontends.mdx

@@ -62,7 +62,7 @@ When creating a frontend after creating the Load Balancer, you can choose which
 
 <Message type="note">
 
-You can attach different frontends to the same backend. They will all forward traffic to this backend. However, you cannot attach multiple backends to the same frontend. To forward traffic from the same frontend to various different backends depending on the client's HTTP Host headers or SNI, create [Routes](/load-balancer/how-to/create-manage-routes/) for your frontend.
+You can attach different frontends to the same backend. They will all forward traffic to this backend. However, you cannot attach multiple backends to the same frontend. To forward traffic from the same frontend to various different backends depending on the client's HTTP Host headers, URL path or SNI, create [Routes](/load-balancer/how-to/create-manage-routes/) for your frontend.
 
 </Message>
 

pages/load-balancer/reference-content/migrating-aws.mdx

@@ -92,7 +92,7 @@ To create the equivalent of an AWS **Application Load Balancer** with Scaleway,
 
 - One or more frontends listening on port 80 or 443
 - One or more backends configured for HTTP or HTTPS protocol
-- (Optional) Routes from frontends to backends based on HTTP Host headers
+- (Optional) Routes from frontends to backends based on HTTP Host headers or URL path
 
 To create the equivalent of an AWS **Network Load Balancer** with Scaleway, you will typically create a Load Balancer with: