Hi again,
On Thu, Jul 01, 2010 at 02:47:46PM +0200, Willy Tarreau wrote:
> Hi,
>
> On Thu, Jul 01, 2010 at 03:05:15PM +0300, Juhani Åhman wrote:
> > > Can you start wireshark or tcpdump session with a working websockets
> > > setup and offer a download of this file, so that we can take alook
> > > what's differrent.
> >
> > you can download wireshark dump here. In it I'm connecting straight to
> > the backend server without haproxy. When I monitored the backend server
> > with haproxy in the middle, I could not get any websocket related
> > packets through. haproxy just discards them.
> >
> > http://a47.org/ws_packets
> >
> > It first establishes a websocket connection, receives message PING from
> > server, send message PONG and then closes the connection.
>
> Thanks for the trace, but could you please take the same one between the
> browser and haproxy ? It's the most important one because it's the one
> where we should see why nothing happens (maybe a "400 bad request" or
> something like this).
When I send your trace through haproxy, I see correct exchanges between
the client and the server. The only thing that *might* be causing trouble
is the "connection: close" header which is added. Could you please try to
configure your instance with both following options set :
option http-server-close
option http-pretend-keepalive
and without "option httpclose" ?
In my case, I get an *exact* copy of the client's request on the server,
as well as an exact copy of the server's response on the client, and both
can continue to talk uninterrupted, so I don't know why it does not work
on your side. BTW I'm on haproxy 1.4.8 too.
Regards,
willy
