Kungani ukwehluleka kwe-SockJS proxy kungavela kuphela ngemva kokubuyela emuva
Indlela ye-WebSocket nokubuyela emuva kwe-XHR kungase kusebenzise amaklayenti e-HTTP ahlukene. Khomba ukuthutha okwehlulayo ngaphambi kokushintsha izilungiselelo zayo ze-proxy.
Lapho i-WebSocket isebenza kunethiwekhi eyodwa kodwa i-SockJS ihluleka kwelinye, kungenzeka ukuthi inethiwekhi yesibili iqale ukubuyela emuva kwe-XHR. Lokho kungashintsha ukusetshenziswa kwe-HTTP okwenza izicelo — ngakho-ke nokulungiselelwa kwe-proxy okusetshenziswayo.
Thola i-URL yokuqala ehlulekile kanye nokuthutha okukhethiwe. I-SockJS ingenza isicelo solwazi lwe-HTTP ngaphambi kokukhetha ukuthutha; i-WebSocket handshake nezicelo zokubuza ezilandelayo kuyimisebenzi ehlukene. Ukulungiselelwa kwe-handshake okusebenzayo akufakazi indlela esetshenziswa kukho ngakunye.
Kuklayenti ye-Java ye-Spring, i-RestTemplateXhrTransport yamukela i-RestTemplate elungiselelwe. Imboni yezicelo zayo kanye neklayenti le-HTTP elingaphansi kunikeza indlela ye-proxy nokuqinisekiswa okusekelwa ukubuyela emuva. Ku-Spring 6 ne-HttpClient 5, lungiselela imboni yezicelo yangempela yaleyo RestTemplate. Uma lokho kusetshenziswa kusebenzisa izingxenye ze-Apache HTTP, isizukulwane sayo kumele sivumelane nokuhlanganiswa.
Iklayenti le-WebSocket linezilungiselelo zalo zokuxhumana ezibhaliwe. Izakhiwo ze-proxy ze-JVM zithinta indlela kuphela uma iklayenti layo eliqondile lizifunda. Qhathanisa izimo ezisebenzayo nezingasebenzi ngokuthutha, ukusetshenziswa kweklayenti, i-proxy ekhethiwe kanye nephutha lokuqala. Uma kuhluleka kuphela i-XHR, landela indlela yayo, ukuqinisekiswa kwayo kanye nezimpendulo zayo ezihlala isikhathi eside esikhundleni sokushintsha kaningi izilungiselelo zeklayenti le-WebSocket elisebenzayo.