Custom Query (2296 matches)
Results (55 - 57 of 2296)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2539 | fixed | --with-http_v3_module changes the layout of the ngx_connection_s structure that can be used by modules, but does not change the signature | ||
Description |
Nginx compiled with v3 support has following signature: ./configure --with-http_v3_module && make -j8 egrep -ao '.,.,.,[01]{34}' objs/nginx 8,4,8,0000111111010111001110111111000110 Nginx compiled without v3 support will have the same signature: ./configure && make -j8 egrep -ao '.,.,.,[01]{34}' objs/nginx 8,4,8,0000111111010111001110101111000110 But nginx compiled with v3 support has different struct ngx_connection_s layout, it has additional 'quic' field - https://trac.nginx.org/nginx/browser/nginx/src/core/ngx_connection.h?rev=58afcd72446ff33811e773f1cabb7866a92a09a0#L153. Thus, if we compile a module for nginx without v3 support and try to load it into nginx with v3 support, the module will be successfully loaded because they have the same versions and signatures, but the module will behave badly due to different structure layouts. |
|||
#2538 | duplicate | Site has TLS 1.2 connection despite being configured with TLS 1.3 only | ||
Description |
Hello, I'm running nginx on Archlinux. |
|||
#2537 | invalid | Host not found in resolver "kube-dns.kube-system.svc.cluster.local". Apparently 'resolver' does not work with long DNS names | ||
Description |
Hi, I have the following simple configuration: / # cat /etc/nginx/conf.d/nginx.conf server { listen 8080; server_name $hostname; location / { root /usr/share/nginx/html; index index.html; try_files $uri $uri/ /index.html; } location /api/ { error_log /var/log/nginx/api-error.log debug; resolver kube-dns.kube-system.svc.cluster.local valid=10s; set $target todo-list-backend-svc.default.svc.cluster.local; proxy_pass http://$target; } Which gives me the following error: / # nginx -s reload 2023/08/26 11:16:25 [emerg] 60#60: host not found in resolver "kube-dns.kube-system.svc.cluster.local" in /etc/nginx/conf.d/nginx.conf:11 nginx: [emerg] host not found in resolver "kube-dns.kube-system.svc.cluster.local" in /etc/nginx/conf.d/nginx.conf:11 I've checked that "kube-dns.kube-system.svc.cluster.local" can be resolved locally: / # nslookup kube-dns.kube-system.svc.cluster.local Server: 10.96.0.10 Address: 10.96.0.10:53 Name: kube-dns.kube-system.svc.cluster.local Address: 10.96.0.10 This is my /etc/resolv.conf: / # cat /etc/resolv.conf nameserver 10.96.0.10 search default.svc.cluster.local svc.cluster.local cluster.local localdomain options ndots:5 When I remove the "svc.cluster.local" from the DNS name, nginx is reloaded without any issue: / # cat /etc/nginx/conf.d/nginx.conf server { listen 8080; server_name $hostname; location / { root /usr/share/nginx/html; index index.html; try_files $uri $uri/ /index.html; } location /api/ { error_log /var/log/nginx/api-error.log debug; resolver kube-dns.kube-system valid=30s; set $target todo-list-backend-svc.default.svc.cluster.local; proxy_pass http://$target; } / # nginx -s reload 2023/08/26 11:20:03 [notice] 67#67: signal process started / # So, what is going wrong here? It looks like resolver is unable to deal with long DNS names. |