-
Notifications
You must be signed in to change notification settings - Fork 81
Description
Bug Overview
See ssl.alpn is defined in stream:
{% if ssl['alpn'] is defined %} |
See it's not defined in http:
{% if ssl['buffer_size'] is defined %} |
See affect when attempting to implement:
servers: - core: listen: - address: 0.0.0.0 port: 80 default_server: true - address: 0.0.0.0 port: 443 ssl: false default_server: true - address: "[::]" port: 80 default_server: true server_name: localhost client_max_body_size: 512k ssl: alpn: http/1.1 certificate: /etc/ssl/certs/molecule.crt certificate_key: /etc/ssl/private/molecule.key ciphers: - HIGH - "!aNull" - "!MD5"
`server {
client_max_body_size 512k;
listen 0.0.0.0:80 default_server;
listen 0.0.0.0:443 default_server;
listen [::]:80 default_server;
server_name localhost;
ssl_certificate /etc/ssl/certs/molecule.crt;
ssl_certificate_key /etc/ssl/private/molecule.key;
ssl_ciphers HIGH:!aNull:!MD5;`
Expected Behavior
Parameter ssl.alpn should be implemented in http configuration
Steps to Reproduce the Bug
Deploy http configuration with ssl.alpn
Notice it does not get implemented
Environment Details
- Target deployment platforms: [e.g. AWS/GCP/local cluster/etc...]
- Target OSs: [e.g. RHEL 9/Ubuntu 24.04/etc...]
- Host OS (where you are running Ansible from): [e.g. RHEL 9/Ubuntu 24.04/etc...]
- Version of the NGINX Ansible role (or specific commit): [e.g. 0.25.0/commit hash]
- Version of Ansible: [e.g. 2.16.5]
- How is Ansible being managed: [e.g. CLI/pipeline/Automation Hub/etc...]
- Version of Jinja2 (if you are using any templating capability): [e.g. 3.1.1]
Additional Context
No response