* feat(openresty): add proxy timeout settings to performance tuning
Expose proxy_connect_timeout, proxy_send_timeout and proxy_read_timeout
at http level, so a slow backend no longer hits the 60s 504 without a
way to raise it from the panel.
The stock nginx.conf does not set them, so an absent directive is shown
with nginx's built-in 60s and only written once changed. Writing it
unconditionally would clash with the same directive set at http level
by an included file and fail the config test.
Time directives now keep their unit suffix like the size directives do.
keepalive_timeout previously dropped it, saving 5m back as 5 seconds,
and its helper text no longer reads as a generic connection timeout.
Refs #13824
* fix(openresty): keep performance settings from overwriting http-level values
Reading the http scope used FindDirectives, which descends into server
and location blocks, while saving writes the http block. A site-level
proxy_read_timeout 2s was shown as the global value and written back
over the global 5m when only gzip was changed. Read only the http
block's own directives.
A directive nginx.conf leaves unset may still be set at the top level
of an included file. Report that value with its file, show it
read-only, and leave it out of the save, instead of showing nginx's
default and writing a duplicate that fails the config test.
Durations are now edited as written and only sent when changed, so
1m30s and keepalive_timeout's second value round-trip intact. Input is
validated against nginx's duration syntax.
Saving is disabled until the current values have loaded, so the form
defaults cannot be written over the real configuration.
Installs that enabled ngx_brotli before v2.3.0 have no http.d include in
nginx.conf, because the include is only inserted when a module is toggled
or built. The settings page reported this as "cannot write the managed
configuration" and skipped the brotli save, so the save path that inserts
the include was never reached, even on a stock nginx.conf.
The settings response now tells the two cases apart with an in-memory
insertion check that writes nothing:
- include missing but insertable, or managed file missing: managedPending,
the page explains the values take effect after saving and saves normally
- no safe insertion point: managedUnavailable, unchanged
The save path now inserts the include through ensureNginxHTTPIncludeActive,
the same function module activation uses, so both produce identical
results. A sentinel error keeps "no insertion point" mapped to
ErrBrotliUnsupported while I/O failures are still returned as-is.
* fix: stop translating the built-in Default group name
* fix: resolve default cronjob group by flag
---------
Co-authored-by: ssongliu <sloooop1x@gmail.com>