Skip to content

PR from Jay #512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 6, 2025
Merged

PR from Jay #512

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
e988344
Commit from Jay
May 4, 2025
cc5700f
Merge branch 'nginx:main' into main
jaypolansky1 May 4, 2025
d125eff
Apply suggestions from code review
mjang May 6, 2025
fb491f8
Update content/nginx/admin-guide/security-controls/securing-http-traf…
mjang May 6, 2025
8cb453a
Update content/nginx/admin-guide/security-controls/securing-http-traf…
mjang May 6, 2025
e292cf3
Merge branch 'main' into main
mjang May 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/nginx/admin-guide/security-controls/securing-http-traffic-upstream.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,14 +25,14 @@ You can purchase a server certificate from a trusted certificate authority (CA).
<span id="client_certs"></span>
## Obtaining an SSL Client Certificate

NGINX will identify itself to the upstream servers with an SSL client certificate. A trusted CA must sign the client certificate, which is configured on NGINX, together with the corresponding private key.
NGINX will identify itself to the upstream servers with an SSL client certificate. A trusted CA must sign the client certificate, which is configured on NGINX together with the corresponding private key.

You will also need to configure the upstream servers to require client certificates for all incoming SSL connections. In addition, you will need to trust the CA that issued the NGINX client certificate. Then, when NGINX connects to the upstream server, it will provide its client certificate and the upstream server will accept it.
You will also need to configure the upstream servers to require client certificates for all incoming SSL connections, and to trust the CA that issued NGINX client certificate. Then, when NGINX connects to the upstream, it will provide its client certificate and the upstream server will accept it.

<span id="config"></span>
## Configuring NGINX

First, change the URL to an upstream group to support SSL connections. Specify the “https” protocol for the proxied server in the NGINX configuration file. Alternatively, [in the proxy_pass](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass) directive, specify an upstream group.)
First, change the URL to an upstream group to support SSL connections. Specify the “https” protocol for the proxied server in the NGINX configuration file. Alternatively, [in the proxy_pass](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass) directive, specify an upstream group.) >>>>>>> main

```nginx
location /upstream {
Expand Down
Loading