On Mon, Feb 3, 2014 at 9:35 PM, Tony Wilk <[email protected]>wrote:
> > > On Monday, February 3, 2014 4:48:57 PM UTC, Sergey Lyubka wrote: >> >> Thank you! >> > *snip* > >> I don't think Mongoose should handle Sec-Websocket-Protocol header, it >> should >> be up to application that embeds Mongoose to reply with the correct >> header. >> Or do you think otherwise? Please let me know! >> > *snip* > > Mongoose would need at least a small mod because if > Sec-Websocket-Protocol is present, then > the handshake reply must also contain that header (otherwise the client > will drop the connection). > Last time I looked, I thought it was Mongoose that builds the websocket > handshake reply. > That's a good point. A handler must be called back on handshake. I'll think about the proper interface. Thanks! -- You received this message because you are subscribed to the Google Groups "mongoose-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mongoose-users. For more options, visit https://groups.google.com/groups/opt_out.
