I-Tornado websocket_connect ayisebenzisi i-CurlAsyncHTTPClient
Hlola ukusekelwa kokuxhumana kwe-WebSocket kwe-Tornado ngokuzimela kusuka ekuhlelweni kwe-CurlAsyncHTTPClient ene-proxy.
Isicelo se-HTTP se-Tornado esisebenza nge-CurlAsyncHTTPClient asikhombisi ukuthi i-websocket_connect isebenzisa i-backend efanayo.
Ukuqaliswa kokuxhumana kwe-WebSocket kwe-Tornado kwakhelwe phezu kwendlela yayo yokuxhumana ye-HTTP. Ukuqaliswa okulula kwe-HTTP kubhala ukuthi izinkambu ze-proxy azisekelwa. Ukuhlela iklayenti le-HTTP elingahambisani nesikhathi lomhlaba wonke ukuthi lisebenzise i-curl akushintshi le ndlela ye-WebSocket ngesixhumi se-proxy se-curl.
Ngakho-ke ukudlulisa into ye-HTTPRequest nakho akubona ubufakazi bokusekelwa kwe-proxy. Into ingase ithwale izinkambu ezingamukelwa ukuqaliswa okukhethiwe. Hlola iphutha nokuqaliswa kwangempela kokuxhumana.
Uma uhlelo ludinga i-WebSocket nge-proxy, khetha ukuhlanganiswa kokuxhumana kwe-WebSocket okubhaliwe okusekela leyo protocol ye-proxy nendlela yokuqinisekisa. Gcina umjikelezo wokuphila kanye nemodeli ye-I/O kuhambisana nohlelo.
Ngemva kokuthi indlela ye-proxy isungulwe, i-WebSocket evikekile isadinga i-TLS yendawo ekholelwa kuyo kanye nokuxhawana kwayo kwe-WebSocket. Isicelo se-HTTP esivamile esisebenzayo asiqinisekisi ngesinye salezi zigaba zakamuva.