Sunan mai masaukin na gaba (forward proxy) ya ɓace daga buƙatar

Buƙatar HTTP ta yau da kullum ta hanyar wakili na gaba tana bayyana inda ake zuwa, don haka Host da sunan mai masaukin Express ba za su iya bambanta sunayen wakilin da kansa ba.

Yi tsammanin east.proxy.example da west.proxy.example suna warwarewa zuwa mai saurare ɗaya na HTTP na wakili. Abokin ciniki da ke amfani da kowane ɗaya daga cikin sunayen zai iya aikawa:

GET http://www.example.org/report HTTP/1.1
Host: www.example.org

Buƙatar tana bayyana gidan yanar gizon. Ba ta ɗauke da sunan wakilin da abokin ciniki ya warware kafin buɗe TCP ba. Don haka sunan mai masauki da Express ya samu daga Host ba zai iya zaɓar hanya bisa waɗannan ƙananan yankunan wakilin ba.

Idan kana da iko kan abokin ciniki da wakili, ba da bayyanannen shigarwar tafarkin hanya. Domin wakilin da ke aiwatar da alamar X-Route:

curl --proxy http://east.proxy.example:8080 \
  --proxy-header 'X-Route: east' \
  https://www.example.org/

--proxy-header yana nufar sadarwa da wakili, har da CONNECT. Kanun -H na yau da kullum a kan buƙatar HTTPS yana cikin musayar HTTP ɓoyayyiyar inda ake zuwa.

Dole ne uwar garken ta aiwatar da manufar tafarkin hanya kuma ta ba da izini, sannan ta cinye alamar ba tare da tura ta zuwa gidan yanar gizon ba. A madadin, yi amfani da wuraren saurare ko asusun wakili da aka saita dabam a matsayin shigarwar tafarkin hanya.

Domin inda ake zuwa na HTTPS, Node yana karɓar buƙatar ramin farko ta hanyar abin da ya faru na connect na uwar garken HTTP ɗinsa. Middleware na buƙatar Express na yau da kullum ba ya kula da wannan abin da ya faru. Maƙasudin CONNECT ɗinsa har yanzu yana bayyana uwar garken inda ake zuwa, ba sunan wakilin ba.

Labarai masu alaƙa