v0.29.0

docs/CUSTOM_LOCATIONS.md

@@ -38,7 +38,7 @@ Encoded separators (`%2f`, `%5c`), encoded `%`, dot segments and other ambiguous
 
 ## Actions
 
-A location can proxy to a backend, serve an existing Web Service, or return a local response.
+A location can proxy to a backend, serve an existing Web Service, return a local response, or redirect the client to another absolute HTTP(S) URL.
 
 ### Proxy
 
@@ -61,7 +61,20 @@ The query string is preserved. Rewrites change only the selected source path; re
 
 `Return custom response` is the equivalent of a simple Nginx `return`: choose an HTTP status from 200 through 599, a Content-Type and a response body. RustProxy does not open a backend connection for this action. `HEAD`, `204` and `304` responses do not send a body.
 
-For a redirect, use a 3xx status and add a `Location` response header in the visual header configurator.
+### Redirect
+
+`Redirect` is a backend-less action. Choose `301`, `302`, `303`, `307` or `308`, set an absolute `http://` or `https://` target, and optionally preserve the incoming query string. RustProxy validates the target and does not allow capture expansion inside the target scheme/authority.
+
+For capture-based path rewriting, configure a separate **Redirect rewrite regex**. Captures can be referenced as `$1` or `${name}` in the redirect target path/query. This separation mirrors an Nginx `location` selector followed by a separate `rewrite` expression. For example, the Nginx pattern:
+
+```nginx
+location ~* \.(?:tar\.gz|zip?)$ {
+    rewrite ^/(.*)$ https://objectstorage.example.invalid/b/repo/o/$1 permanent;
+}
+```
+
+corresponds to a case-insensitive regex Custom location `\.(?:tar\.gz|zip?)$`, action **Redirect**, status `301`, target `https://objectstorage.example.invalid/b/repo/o/$1`, and redirect rewrite regex `^/(.*)$`. Query preservation is controlled independently.
+
 
 ## Request and response headers