Generates the nginx rules for prerendered pages
Pages now map to their html file, other forms get one redirect, unknown URLs get a real 404 and responses are compressed. A browser-free test suite runs the rules against a real nginx, in CI only so far. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
+2
@@ -78,6 +78,8 @@ The proxy Pi handles TLS through certbot and forwards `test.andreaslop.nl` to `1
|
||||
| `proxy_cache` | An old SPA `index.html` could stay cached for `/over-mij` |
|
||||
| `proxy_redirect` | Could change the relative 301s |
|
||||
|
||||
**Checked by the owner on 2026-11-01, reported through the Pi-Main session: no change needed on the proxy Pi.** The server block has `proxy_pass http://192.168.1.103` with Host, X-Forwarded-Proto, X-Forwarded-For and X-Real-IP, and no `proxy_http_version` (so HTTP/1.0 upstream), no change to `Accept-Encoding`, no `proxy_intercept_errors` and no `add_header`. At http level there is no gzip, `proxy_cache`, `add_header` or `proxy_buffering`. So `gzip_http_version 1.0` must stay in the new block, all headers and the 404 page come from the hosting Pi, and no cache holds old pages. `http2 on;` in the 443 block is an optional, separate improvement, out of scope for this feature.
|
||||
|
||||
The proxy passes an already compressed response through unchanged. If the owner wants gzip for all sites, WordPress included, the proxy Pi is the place for that, and this block can keep its own.
|
||||
|
||||
## Points for the generated config
|
||||
|
||||
Reference in New Issue
Block a user