v0.25.0

docs/CUSTOM_LOCATIONS.md

@@ -38,7 +38,7 @@ Encoded separators (`%2f`, `%5c`), encoded `%`, dot segments and other ambiguous
 
 ## Actions
 
-A location can either proxy to a backend or return a local response.
+A location can proxy to a backend, serve an existing Web Service, or return a local response.
 
 ### Proxy
 
@@ -51,7 +51,11 @@ Supported path transformations:
 - **Replace prefix** — replace the matched prefix with another normalized path prefix.
 - **Regex rewrite** — available for regex locations; Rust regex captures can be referenced as `$1` or `${1}` in the replacement.
 
-The query string is preserved. Rewrites change only the upstream path; cache identity remains based on the public client URL.
+The query string is preserved. Rewrites change only the selected source path; reverse-proxy cache identity remains based on the public client URL.
+
+### Web Server
+
+`Web Server` selects one reusable service previously created in the **Web Server** workspace. The location stores only the Web Service ID; document root, index list and directory-listing policy remain in that shared service. Existing location matching and path rewriting are reused, but backend pinning and reverse-proxy object-cache controls do not apply to local files. See [WEB_SERVER.md](WEB_SERVER.md).
 
 ### Local response
 
@@ -93,4 +97,4 @@ Authentication, vhost rate limits, country policy, security headers, compression
 
 ## What is intentionally not an Nginx parser
 
-Custom locations do **not** execute arbitrary Nginx directives or configuration snippets. RustProxy does not currently implement location-level `try_files`, filesystem aliases/roots, embedded scripting, arbitrary `if` expressions or arbitrary module directives. Use the explicit UI controls and the documented JSON schema instead; unknown fields are rejected on save.
+Custom locations do **not** execute arbitrary Nginx directives or configuration snippets. RustProxy does not currently implement location-level `try_files`, per-location filesystem aliases/roots, embedded scripting, arbitrary `if` expressions or arbitrary module directives. Static roots are defined only by reusable Web Services. Use the explicit UI controls and the documented JSON schema instead; unknown fields are rejected on save.