• Deomid Ryabkov's avatar
    Fix handling of WS handshake error response · 1e9fabe1
    Deomid Ryabkov authored
    Check response code, make sure it's 101.
    Pass http_message to the client to keep it appraised.
    This represents a slight change in the API -
    in case of an error MG_EV_WEBSOCKET_HANDSHAKE_DONE will now be delivered where previosuly connection would just hang.
    Clients that do not examine the argument may for a moment think handshake has succeeded but in fact connection will be closed immediately.
    
    CL: mg: Fix handling of WS handshake error response
    
    PUBLISHED_FROM=645a43d9e5bee216e54411f85827c9b974e9a7d1
    1e9fabe1
Name
Last commit
Last update
..
intro.md Loading commit data...
mg_connect_ws.md Loading commit data...
mg_connect_ws_opt.md Loading commit data...
mg_http_is_authorized.md Loading commit data...
mg_http_send_digest_auth_request.md Loading commit data...
mg_printf_websocket_frame.md Loading commit data...
mg_send_websocket_frame.md Loading commit data...
mg_send_websocket_framev.md Loading commit data...
mg_send_websocket_handshake.md Loading commit data...
mg_send_websocket_handshake2.md Loading commit data...
mg_send_websocket_handshake3.md Loading commit data...
mg_send_websocket_handshake3v.md Loading commit data...
mg_set_protocol_http_websocket.md Loading commit data...
mg_url_decode.md Loading commit data...
struct_http_message.md Loading commit data...
struct_mg_http_multipart_part.md Loading commit data...
struct_mg_ssi_call_ctx.md Loading commit data...
struct_websocket_message.md Loading commit data...