I'm playing with ngx_http_perl_module; for starters, just logging to error_log and setting headers: location / { set $target https://$host$request_uri; perl ph::handler; add_header X-debug-message "redirect target: $target" always; return 302 $target; } However, if I have that return 302 in there,by abatie - How to...
I believe this is related to blocking neighbor discovery on the address for the purposes of doing direct server return load balancing, and not nginx related, thanks!by abatie - Nginx Mailing List - English
OK, that's odd: I commented out the ipv4 address and it still fails. It's not a conflict then, so something's odd in the network stack...by abatie - Nginx Mailing List - English
Yup: eth0 Link encap:Ethernet HWaddr 00:50:56:8C:62:77 inet addr:207.55.17.91 Bcast:207.55.19.255 Mask:255.255.252.0 inet6 addr: fe80::250:56ff:fe8c:6277/64 Scope:Link inet6 addr: 2607:f678::17:79/64 Scope:Global inet6 addr: 2607:f678::17:91/64 Scope:Global And what's odd is when I first tried it, it worked.by abatie - Nginx Mailing List - English
I have nginx binding to a variety of addresses for ssl and target selection reasons. Now I'm trying to add ipv6 support. Since I'm using specific listen addresses, I wouldn't expect to have a binding conflict, however I am, and I'm hoping someone can point me in the right direction: server { listen 207.55.17.79:25; ... server { listen [2607:f678::17:79]:25; ... <mailproxyby abatie - Nginx Mailing List - English