v0.29.4

docs/PHP_FPM.md

@@ -13,7 +13,36 @@ Request
   -> existing error/header/logging/metrics/transport pipeline
 ```
 
-Vhosts and locations still reference only a Web Service. PHP settings remain part of that reusable service.
+Vhosts and locations still reference only a Web Service. Each Web Service may
+use local PHP settings or reference a shared `php_fpm_profiles` entry from the
+normal revisioned configuration; its local settings are retained on detach.
+
+### Shared PHP-FPM profiles (0.29.4)
+
+In **Web Server → Edit Web Service → PHP-FPM**, select **Local configuration**
+or a named profile. **Manage PHP-FPM profiles** opens a modal with an expandable
+editor for every profile and an **Add profile** action. A profile contains the
+same PHP execution, FastCGI and PHP_VALUE/PHP_ADMIN_VALUE settings as local
+configuration. Changes to a shared profile affect all attached services after
+validation and apply. In-use profiles cannot be deleted.
+
+Configuration example:
+
+```json
+{
+  "php_fpm_profiles": [{
+    "id": "php82", "name": "PHP 8.2 FPM",
+    "php": {"enabled": true, "endpoint": "unix:/run/php/php8.2-fpm.sock"}
+  }],
+  "web_services": [{
+    "id": "site", "name": "Site", "document_root": "/var/www/site",
+    "php_profile_id": "php82"
+  }]
+}
+```
+
+Unspecified PHP fields inherit the safe serde defaults. A service without
+`php_profile_id` uses its own `php` object as in earlier versions.
 
 ## Runtime model
 
@@ -173,7 +202,14 @@ PHP stderr is bounded by `stderr_log_bytes` and written to the RustProxy diagnos
 
 PHP output does not use static file validators or the static-file OS representation path. Application response headers and the normal vhost/location response-header pipeline control client/intermediary caching.
 
-The Web Service static `cache_rules` apply to local static file responses, not to PHP stdout. RustProxy does not silently place PHP responses into a new Web Server object cache.
+The Web Service static `cache_rules` apply to local static file responses, not
+to PHP stdout. When global/vhost caching is enabled, explicitly cacheable
+PHP-FPM responses may enter the shared RustProxy cache; responses with
+`Set-Cookie`, `Cache-Control: private` or `no-store` cannot be stored. In
+particular, do not enable forced caching of authenticated WordPress pages
+without auditing the origin response policy. HTTP/2 and HTTP/3 `:authority`
+requests populate the `HTTP_HOST` FastCGI parameter, retaining the original
+host/port from the incoming request when provided.
 
 ## PHP installation