Tornado websocket_connect ba ya amfani da CurlAsyncHTTPClient

Buƙatar HTTP ta Tornado da ke aiki ta CurlAsyncHTTPClient ba ta tabbatar da cewa websocket_connect yana amfani da wannan backend ɗin ba.

Aiwatar da haɗin WebSocket a Tornado yana ginuwa a kan hanyar haɗin HTTP ta kansa. Aiwatarwar HTTP mai sauƙi ta rubuta cewa filayen proxy ba a tallafa musu ba. Saita babban abokin ciniki na HTTP async don amfani da curl ba ya maye gurbin wannan hanyar WebSocket da mai haɗa proxy na curl.

Don haka ba da wani abu na HTTPRequest shima ba hujja ba ce ta tallafin proxy. Abun na iya ɗauke da filayen da aiwatarwar da aka zaɓa ba ta karɓa ba. Duba kuskuren da ainihin aiwatarwar haɗin.

Idan aikace-aikacen yana buƙatar WebSocket ta hanyar proxy, zaɓi haɗin WebSocket da aka rubuta wanda ke tallafawa wannan ka'idar proxy da hanyar tantancewa. Ka kiyaye zagayowar rayuwarsa da tsarin I/O ɗinsa su dace da aikace-aikacen.

Bayan an kafa hanyar proxy, WebSocket mai tsaro har yanzu yana buƙatar TLS na manufa da musafaha na WebSocket. Buƙatar HTTP ta yau da kullum da ke aiki ba ta tabbatar da ɗaya daga cikin waɗannan matakan na baya ba.