a150c27c1d9a6
> # Parent fac6ad94e062ee30356338c943843c4b34d5f532
> Tests: http resolver with ipv4/ipv6 parameters.
>
Looks good.
--
Sergey Kandaurov
___
nginx-devel mailing list -- nginx-devel@nginx.org
To unsubscribe send an email to nginx-devel-le...@nginx.org
# HG changeset patch
# User Eugene Grebenschikov
# Date 1665082566 25200
# Thu Oct 06 11:56:06 2022 -0700
# Node ID 061aa601e6a33ed9e8671fbd3c2a150c27c1d9a6
# Parent fac6ad94e062ee30356338c943843c4b34d5f532
Tests: http resolver with ipv4/ipv6 parameters.
diff -r fac6ad94e062 -r
# HG changeset patch
# User Eugene Grebenschikov
# Date 1665038181 25200
# Wed Oct 05 23:36:21 2022 -0700
# Node ID 595dee133b0a3681e95567368191c559ad89b3a1
# Parent fac6ad94e062ee30356338c943843c4b34d5f532
Tests: http resolver with ipv4/ipv6 parameters.
diff -r fac6ad94e062 -r
122b
> # Parent c2c188c914880df9a04706482b809329aef29467
> Tests: http resolver with ipv4/ipv6 parameters.
>
> diff -r c2c188c91488 -r 238226015a21 http_resolver_ipv4.t
> --- /dev/null Thu Jan 01 00:00:00 1970 +
> +++ b/http_resolver_ipv4.tTue Oct 04 00:35:42 2022 -0700
> @@ -0,0 +1,208 @@
&g
Patch subject is complete summary.
# HG changeset patch
# User Eugene Grebenschikov
# Date 1664868942 25200
# Tue Oct 04 00:35:42 2022 -0700
# Node ID 238226015a212a0786cf720a214bc0eec60c122b
# Parent c2c188c914880df9a04706482b809329aef29467
Tests: http resolver with ipv4/ipv6 parameters
I have a virtual server with Debian Wheezy and nginx 1.4.4 installed:
nginx version: nginx/1.4.4
TLS SNI support enabled
configure arguments: --prefix=/usr/share/nginx
--conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log
--http-client-body-temp-path=/var/lib/nginx/body
Hello,
It seems I solved the problem...
It was indeed by reading a little more carefully the doc
http://wiki.nginx.org/HttpCoreModule#listen, thanks @Lukas! ;o)
The '*:80' syntax is used for IPv4 listening, I don't understand why it
works as-is for you Ted. Maybe Maxim will be of a better help
That's exactly what I tried first, and if there are multiple servers
listening to same ports, I get the following error:
nginx: [emerg] duplicate listen options for [::]:80 in
/etc/nginx/conf.d/***.conf:3
See follow-up messages or (through the forum archive on this subject):
On Apr 5, 2013, at 4:17 PM, B.R. reallfqq-ng...@yahoo.fr wrote:
Is there any other way to allow Nginx ot listen on both interface types
without mandatory system configuration?
I just have listen *:80 in my configurations, and it works fine over IPv4 and
IPv6.
Everything you need to know:
http://nginx.org/en/docs/http/ngx_http_core_module.html#listen
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
@Maxim
I tried the duplicate configuration entries:
listen 80;
listen [::]:80 ipv6only=on;
I has the following error:
nginx: [emerg] duplicate listen options for [::]:80 in
/etc/nginx/conf.d/***.conf:3
@Ted
I tested your solution but as I expected nginx is only listening on IPv4
Hello!
On Fri, Apr 05, 2013 at 06:07:23PM -0400, B.R. wrote:
Hello,
@Maxim
I tried the duplicate configuration entries:
listen 80;
listen [::]:80 ipv6only=on;
I has the following error:
nginx: [emerg] duplicate listen options for [::]:80 in
/etc/nginx/conf.d/***.conf:3
If you have
Hmm...
@Maxim
I guess I haven't understood your piece of advice, since 'listen' can only
be used in 'server' directive...
What is it you wanted me to try, again? :oD
---
*B. R.*
On Fri, Apr 5, 2013 at 8:02 PM, B.R. reallfqq-ng...@yahoo.fr wrote:
I have indeed several virtual servers.
I have
13 matches
Mail list logo
