Re: Application Persistence with WebSockets

2014-09-16 Thread Willy Tarreau
Hi Ryan, On Mon, Sep 15, 2014 at 12:11:39PM -0500, Ryan Brock wrote: Willy, I tested these changes in my environment and it all works. So you may move forward with these changes. Great, thanks for the feedback! I really appreciate the help. You're welcome :-) Best regards, Willy

Re: Application Persistence with WebSockets

2014-09-15 Thread Ryan Brock
Willy, I tested these changes in my environment and it all works. So you may move forward with these changes. I really appreciate the help. - Ryan Brock On Thu, Sep 11, 2014 at 12:59 AM, Willy Tarreau w...@1wt.eu wrote: Hi Ryan, On Wed, Sep 10, 2014 at 04:36:24PM -0500, Ryan Brock wrote:

Re: Application Persistence with WebSockets

2014-09-11 Thread Willy Tarreau
Hi Ryan, On Wed, Sep 10, 2014 at 04:36:24PM -0500, Ryan Brock wrote: Here is the change I made on the very latest 1.6 master dev. It is only in the one spot. There was discussion of changing it in a few other spots were status was checked for less than 200, but I wouldn't know how to test that

Re: Application Persistence with WebSockets

2014-09-10 Thread Ryan Brock
Here is the change I made on the very latest 1.6 master dev. It is only in the one spot. There was discussion of changing it in a few other spots were status was checked for less than 200, but I wouldn't know how to test that correctly so I didn't feel it was a good idea to change it. This change

RE: Application Persistence with WebSockets

2014-08-28 Thread Ryan Brock
I can do it. I should learn the process for submitting changes anyway. I'll base it on 1.6. Thanks for the help. Really appreciate it. - Ryan On Aug 28, 2014 7:18 AM, Lukas Tribus luky...@hotmail.com wrote: Hi Willy, I think that experimenting with (txn-status 200 txn-status != 101)

Re: Application Persistence with WebSockets

2014-08-28 Thread Willy Tarreau
On Thu, Aug 28, 2014 at 07:25:07AM -0500, Ryan Brock wrote: I can do it. I should learn the process for submitting changes anyway. I'll base it on 1.6. Thanks for the help. Really appreciate it. Thanks Ryan. There's nothing fundamental in the way to submit changes. If you want to ensure

Re: Application Persistence with WebSockets

2014-08-25 Thread Ryan Brock
I apologize, but I am not sure the usual procedure regarding changes. What is the next step? Should I put together a change that simply looks for status codes less than 200, but that is not 101? Or did we need more discussion? I see your point about HSTS. I am not familiar enough with HAProxy

RE: Application Persistence with WebSockets

2014-08-25 Thread Lukas Tribus
Hi Ryan, I apologize, but I am not sure the usual procedure regarding changes. What is the next step? Should I put together a change that simply looks for status codes less than 200, but that is not 101? Or did we need more discussion? I would like to hear Willy's opinion about

Re: Application Persistence with WebSockets

2014-08-20 Thread Lukas Tribus
Hi Ryan, I recently started investigating using HAProxy to ensure that multiple  WebSocket connections from the same browser (or device) end up  communicating with the same application server. Forwarding all  connections from the same origin to the respective application server  greatly