thank you for addressing all my questions, I think I am on the right path
now.
On Mon, May 13, 2013 at 12:50 AM, Baptiste wrote:
> Hi,
>
> Since all first request won't have the cookie (whatever the browser),
> the only way to fix your issue is to use source IP laod-balancing or
> source IP per
Hi,
Since all first request won't have the cookie (whatever the browser),
the only way to fix your issue is to use source IP laod-balancing or
source IP persistence, don't make any difference between browsers.
Baptiste
On Mon, May 13, 2013 at 8:41 AM, Peter Saitz wrote:
> 3. is there a way for
3. is there a way for haproxy to detect this scenario? Or how would I
create special block of options/rules for such clients in haproxy config?
If yes, can you provide some example? I am digging into this mainly because
IE is not sending all headers when sending cross-origin request (not sure
if th
Hi,
My answers inline.
On Sun, May 12, 2013 at 11:25 PM, Peter Saitz wrote:
> 1. For http, I should set this to balanace roundrobin and haproxy is
> attaching A or B to the cookie, if this A or B is present in cookie for any
> following incoming request, then user is directed
> to the same ser
3. If cookie is not accepted by client's browser, how can I ensure that all
those clients are redirected to a single server?
On Sun, May 12, 2013 at 2:21 PM, Peter Saitz wrote:
> I see, hmm, reason why I went this way originally was to ensure stickiness
> of single browser session. I think I sl
I see, hmm, reason why I went this way originally was to ensure stickiness
of single browser session. I think I slightly misunderstood the haproxy
documentation first time I red it.
Is this how it works?
1. For http, I should set this to balanace roundrobin and haproxy is
attaching A or B to the c
On Sat, May 11, 2013 at 10:47 PM, Peter Saitz wrote:
> A side question: all traffic is directed to B server (second server in
> configuration), the BAYEUX_BROWSER cookie is attached but it is always the
> "B" one. I have no clue what is wrong, do you see any problem why http
> traffic should go to
I took tcpdump and confirmed that x-forwarded-for is there, so it works
correctly, thank you for clearing this issue up for me.
A side question: all traffic is directed to B server (second server in
configuration), the BAYEUX_BROWSER cookie is attached but it is always the
"B" one. I have no clue
Hi Peter,
At first sight, I can't see any reason why HAProxy would not insert
the X-Forwarded-For header.
Baptiste
On Sat, May 11, 2013 at 7:26 PM, Peter Saitz wrote:
> One more question if I may:
>
> The haproxy.cfg file I attached, if you examine it, does options there make
> haproxy attach x
One more question if I may:
The haproxy.cfg file I attached, if you examine it, does options there make
haproxy attach x-forwarded-for header to the http upgrade message?
On Fri, May 10, 2013 at 10:06 PM, Peter Saitz wrote:
> Thank you guys, I think you pretty much explained and cover it to su
Thank you guys, I think you pretty much explained and cover it to such
depth that it is quite clear to me now. I use haproxy as a load balancer,
not sure it I want it to be a transparent proxy. I will try to capture and
retain ip upon the upgrade/handshake request.
On Fri, May 10, 2013 at 2:14 PM
On Fri, May 10, 2013 at 10:56:48PM +0200, Baptiste wrote:
> euh
> That's what I said. You can only insert it during the websocket
> establishment phase.
That's why I said I "partially" disagreed. I disagreed with the sentence
that the only solution was the transparent proxy. The only solution
euh
That's what I said. You can only insert it during the websocket
establishment phase.
I think Peter wants to have the IP information for each data sent by
the client on the websocket. which is not doable.
Well, that's my understanding.
Baptiste
On Fri, May 10, 2013 at 10:30 PM, Willy Tarr
On Fri, May 10, 2013 at 10:52:26AM +0200, Baptiste wrote:
> Hi,
>
> Websocket is not HTTP.
> So HAProxy can't insert a HTTP header in somthing which is not HTTP.
>
> There is an HTTP phase, the websocket establishment in which HAProxy
> can insert the client IP, but after, this is not possible.
>
Hi,
Websocket is not HTTP.
So HAProxy can't insert a HTTP header in somthing which is not HTTP.
There is an HTTP phase, the websocket establishment in which HAProxy
can insert the client IP, but after, this is not possible.
Your only failover is transparent proxy, in my humble opinion.
More info
I am having problem where my app server is not able
to retrieve X-FORWARDED-FOR being behind haproxy and using websockets. It
works when websockets are not used, only plain http. The haproxy cfg is
pretty simple, but I guess there is a problem I do not see in the config
file.
I am attaching my hap
16 matches
Mail list logo
