Nginx 1.19.4 Mainline Release Introduces New Proxy SMTP Auth and SSL Handshake Rejection Features

The nginx 1.19.4 mainline release adds new directives such as proxy_smtp_auth, several ssl_conf_command variants, and ssl_reject_handshake, with the latter allowing servers to reject SSL handshakes for specified hostnames, as demonstrated by example configuration snippets.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
Nginx 1.19.4 Mainline Release Introduces New Proxy SMTP Auth and SSL Handshake Rejection Features

nginx 1.19.4 mainline version has been released, adding several new directives.

Feature: mail proxy adds "proxy_smtp_auth" directive

Feature: new "ssl_conf_command", "proxy_ssl_conf_command", "grpc_ssl_conf_command" and "uwsgi_ssl_conf_command" directives

Feature: new "ssl_reject_handshake" directive

The ssl_reject_handshake directive, located in the ngx_http_ssl_module, when enabled, causes the server block to reject SSL handshakes.

Syntax: ssl_reject_handshake on | off; Default: ssl_reject_handshake off; Context: http, server Example configuration that rejects SSL handshakes for all server names except example.com:

server {
    listen 443 ssl;
    ssl_reject_handshake on;
}

server {
    listen 443 ssl;
    server_name example.com;
    ssl_certificate example.com.crt;
    ssl_certificate_key example.com.key;
}
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

BackendProxyWeb serverSSLDirective
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.