On Thursday 27 March 2014 09:02:57 Xiaochen Wang wrote:
hi
On Thu, Mar 27, 2014 at 1:01 AM, Valentin V. Bartenev
vb...@nginx.comwrote:
On Wednesday 26 March 2014 12:30:11 Xiaochen Wang wrote:
In our production, sometimes, the disk was full. In which case, the
requests
after the
Hello,
Should proxy_pass retry ipv4 if ipv6 fails? Currently (1.5.12), it
does not, and there is no way to force proxy_pass to always use ipv4.
Specifically, if a proxy_pass host has dual records (A+),
proxy_pass seems to only try the .
I'm considering submitting a patch if there is
Hello!
On Thu, Mar 27, 2014 at 12:29:03PM -0400, Jim Popovitch wrote:
Should proxy_pass retry ipv4 if ipv6 fails? Currently (1.5.12), it
does not, and there is no way to force proxy_pass to always use ipv4.
In no particular order:
- The proxy_next_upstream is expected to retry by default.
On Thu, Mar 27, 2014 at 12:59 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 12:29:03PM -0400, Jim Popovitch wrote:
Should proxy_pass retry ipv4 if ipv6 fails? Currently (1.5.12), it
does not, and there is no way to force proxy_pass to always use ipv4.
In no
Hello!
On Thu, Mar 27, 2014 at 04:34:37PM +0100, Trygve Vea wrote:
# HG changeset patch
# User Trygve Vea trygve@redpill-linpro.com
# Date 1395933815 -3600
# Thu Mar 27 16:23:35 2014 +0100
# Node ID 13e6a37c2f57443b0d5dd0abce8d9d4ab00e31e3
# Parent
Hello!
On Thu, Mar 27, 2014 at 01:12:18PM -0400, Jim Popovitch wrote:
On Thu, Mar 27, 2014 at 12:59 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 12:29:03PM -0400, Jim Popovitch wrote:
Should proxy_pass retry ipv4 if ipv6 fails? Currently (1.5.12), it
On Thu, Mar 27, 2014 at 1:27 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 01:12:18PM -0400, Jim Popovitch wrote:
On Thu, Mar 27, 2014 at 12:59 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 12:29:03PM -0400, Jim Popovitch wrote:
- Opprinnelig melding -
Hello!
Hello!
On Thu, Mar 27, 2014 at 04:34:37PM +0100, Trygve Vea wrote:
# HG changeset patch
# User Trygve Vea trygve@redpill-linpro.com
# Date 1395933815 -3600
# Thu Mar 27 16:23:35 2014 +0100
# Node ID
Hi Trygve,
Added so_freebind and so_transparent to the listen directive
This solves a Linux/IPv6-specific problem.
To be able to listen to an IPv6 address that is not yet available on the host,
one need to use the IP_FREEBIND and IP_TRANSPARENT socket options.
The use case in question is
- Opprinnelig melding -
Hi Trygve,
Added so_freebind and so_transparent to the listen directive
This solves a Linux/IPv6-specific problem.
To be able to listen to an IPv6 address that is not yet available on the
host,
one need to use the IP_FREEBIND and IP_TRANSPARENT
10 matches
Mail list logo