Skip to content

Add support for extra_http_parameters per vhost#255

Open
rlenferink wants to merge 1 commit into
geerlingguy:masterfrom
rlenferink:feature/add-extra-http-parameters
Open

Add support for extra_http_parameters per vhost#255
rlenferink wants to merge 1 commit into
geerlingguy:masterfrom
rlenferink:feature/add-extra-http-parameters

Conversation

@rlenferink

Copy link
Copy Markdown

This adds support for vhost HTTP parameters outside the server block (e.g. for Websocket proxying).

Example:

  - listen: "80"
    server_name: "code.loc"
    extra_http_parameters: |
      map $http_upgrade $connection_upgrade {
          default upgrade;
          ''      close;
      }
    extra_parameters: |
      location / {
          proxy_pass http://container-vm1.loc:8443/;

          proxy_set_header Host $host;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          proxy_set_header X-Forwarded-Host $host;
          proxy_set_header X-Forwarded-Proto $scheme;
          proxy_redirect off;
          proxy_http_version 1.1;

          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection $connection_upgrade;
      }

Xref: https://nginx.org/en/docs/http/websocket.html

@github-actions

Copy link
Copy Markdown

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions Bot added the stale label Nov 29, 2025
@rlenferink

Copy link
Copy Markdown
Author

@geerlingguy do you see any possibility to review this change?

@github-actions github-actions Bot removed the stale label Dec 6, 2025
@shakalandy

Copy link
Copy Markdown

@geerlingguy do you see any possibility to review this change?

Can we get this one merged, please? It makes sense and helps with more flexibility.

@github-actions

Copy link
Copy Markdown

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions Bot added the stale label Apr 11, 2026
@rlenferink

Copy link
Copy Markdown
Author

@geerlingguy any chance to get this merged?

@github-actions github-actions Bot removed the stale label Apr 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants