On Mon, Dec 09, 2013 at 10:03:29PM +1030, SplitIce wrote:
> Im not sure that patch would suit my needs, simply because most of the time
> I am matching on the upstream address only and need it to work regardless
> of the port (i.e a regex match on just the IP component).
>
> Perhaps your patch cou
Im not sure that patch would suit my needs, simply because most of the time
I am matching on the upstream address only and need it to work regardless
of the port (i.e a regex match on just the IP component).
Perhaps your patch could be extended to support -
map $upstream_peer_addr $bind_addr {
On Sat, Nov 23, 2013 at 12:15:28PM +1030, SplitIce wrote:
> Attached is the patch,
>
> This is the first time I have created a variable or really done anything
> inside the http request processing flow so feel free to let me know if
> there is a better way to do something or if I have any edge cas
Attached is the patch,
This is the first time I have created a variable or really done anything
inside the http request processing flow so feel free to let me know if
there is a better way to do something or if I have any edge cases.
This patch provides a $upstream_connecting variable which conta
Ruslan, its funny you should mention this, I am testing a patch to do just
that at the moment.
Once I am certain that its not leaking memory and I have reviewed it in
regards to the nginx code standards Ill post it in this email thread in
case it is of use for others.
On Fri, Nov 22, 2013 at 11:
On Tue, Nov 19, 2013 at 09:09:34PM +1030, SplitIce wrote:
> An IPv6 based fallback is not the only solution we want to support,
> ultimately we would like to be able to load-balance between them as well.
> An error_page based solution would not assist.
>
> I also get the feeling that such a hack w
An IPv6 based fallback is not the only solution we want to support,
ultimately we would like to be able to load-balance between them as well.
An error_page based solution would not assist.
I also get the feeling that such a hack would have large implications,
while either an additional parameter o
Hello!
On Mon, Nov 18, 2013 at 10:24:43PM +1030, SplitIce wrote:
> Hi,
>
> We use proxy_bind to ensure traffic always goes out via the same address as
> the incoming request i.e the bound address where a server has many
> addresses. This is a hard restriction in our use case.
>
> We are looking
Hi,
We use proxy_bind to ensure traffic always goes out via the same address as
the incoming request i.e the bound address where a server has many
addresses. This is a hard restriction in our use case.
We are looking to add support for IPv6 backends, we would like to allocate
a single IPv6 outgoi
Hello!
On Sat, Nov 16, 2013 at 11:04:20PM +1030, SplitIce wrote:
> Looking at the documentation it seems there is no way to specify a proxy
> bind address for both IPv4 and IPv6.
>
> You can specify one or the other, but never both. This is a particular
> issue when a configuration is setup to a
Looking at the documentation it seems there is no way to specify a proxy
bind address for both IPv4 and IPv6.
You can specify one or the other, but never both. This is a particular
issue when a configuration is setup to allow for a failure in IPv6 transit
/ routing.
Is it possible to get a proxy_
11 matches
Mail list logo
