Add HTTP_HOST param, cleanup headers, and add WordPress HTTP/3 templates #5185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5184
Summary
This update improves WordPress Nginx templates, adds HTTP/3 support, and introduces automation for selective
reuseportusage.Changes
1. Added missing FastCGI parameter
fastcgi_param HTTP_HOST $host;to all WordPress-related Nginx templates.2. Removed unused directive
proxy_hide_header Upgrade;from multiple.stpltemplates where it was not applicable to FastCGI setups.3. New HTTP/3 WordPress templates and scripts
Introduced new templates and helper scripts with built-in HTTP/3 (QUIC) support:
wordpress-disable-xmlrpc-http3.shwordpress-disable-xmlrpc-http3.stplwordpress-disable-xmlrpc-http3.tplwordpress-http3.shwordpress-http3.stplwordpress-http3.tplwordpress_mu_subdir-http3.shwordpress_mu_subdir-http3.stplwordpress_mu_subdir-http3.tpl4. Reuseport automation
reuseportonly for one site when multiple domains share the same IP, avoiding listener conflicts while supporting HTTP/3.