Hello Willy,
- On 17 May, 2015, at 14:16, Willy Tarreau w...@1wt.eu wrote:
> Hello Phil,
>
> On Tue, May 12, 2015 at 07:54:35AM +0100, Phil Daws wrote:
> (...)
>> the issue is that if I go to the web site via HTTPS, which does not pass
>> through a CDN, then the correct client IP is being pa
Hello Phil,
On 5/12/2015 8:54 AM, Phil Daws wrote:
the issue is that if I go to the web site via HTTPS, which does not pass
through a CDN, then the correct client IP is being passed through but if I go
via HTTP its the CDN's IP which is being presented. When I was using
real_ip_header x-forw
Hello Phil,
On Tue, May 12, 2015 at 07:54:35AM +0100, Phil Daws wrote:
(...)
> the issue is that if I go to the web site via HTTPS, which does not pass
> through a CDN, then the correct client IP is being passed through but if I go
> via HTTP its the CDN's IP which is being presented. When I was
Any thoughts please ?
- Original Message -
From: "Phil Daws"
To: haproxy@formilux.org
Sent: Tuesday, 12 May, 2015 07:54:35
Subject: send-proxy and x-forward-for
Hello:
am testing NGINX behind HAP 1.5.11 and having trouble to understand how
send-proxy should be used with a c
Hello:
am testing NGINX behind HAP 1.5.11 and having trouble to understand how
send-proxy should be used with a combination of x-forward-for. What I so far
in my haproxy.cfg is as follows:
frontend frontend-web-http
mode http
bind 192.168.8.70:80
default_backend backend
5 matches
Mail list logo