wmantly
4f1fce367e
- The edit form's "Parent Wildcard" option stayed greyed out even when a valid wildcard existed, since hostEditOpen() never ran the eligibility check (only the host field's keyup handler did, which setting .val() programmatically doesn't fire) -- and the check itself, GET /host/lookup/:item, had the same self-match bug as the recently-fixed Host.prototype.update() case: it resolves an already-existing host to its own record instead of a sibling wildcard. Added a dedicated /host/wildcard-parent/:item route combining lookUp() (handles a brand-new subdomain) with lookUpWildcardParent() (handles an already-existing host), and hostEditOpen() now actually runs it. - Migrated ops/nginx_conf/autossl.conf's deprecated "listen ... http2" directive to the standalone "http2 on;" directive (nginx 1.25.1+). Bumps to v1.1.12. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KDEx8ghuZR61pqPXc6da9C
24 lines
680 B
Plaintext
24 lines
680 B
Plaintext
listen 443 ssl;
|
|
listen 4443 ssl;
|
|
# The "http2" listen parameter is deprecated since nginx 1.25.1 in favor of
|
|
# this standalone directive, which applies to every "listen ... ssl" in the
|
|
# server block (both 443 and 4443 here).
|
|
http2 on;
|
|
|
|
ssl_protocols TLSv1.2 TLSv1.3;
|
|
ssl_prefer_server_ciphers on;
|
|
ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:!3DES:!MD5;
|
|
|
|
ssl_certificate_by_lua_block {
|
|
auto_ssl:ssl_certificate()
|
|
}
|
|
|
|
location /.well-known/acme-challenge/ {
|
|
content_by_lua_block {
|
|
auto_ssl:challenge_server()
|
|
}
|
|
}
|
|
|
|
ssl_certificate /etc/ssl/resty-auto-ssl-fallback.crt;
|
|
ssl_certificate_key /etc/ssl/resty-auto-ssl-fallback.key;
|