Me ya sa Squid ke rubuta mai masaukin HTTPS amma ba hanyar shafin ba
Ya bayyana hanyoyin HTTPS da suka ɓace a cikin rajistan Squid CONNECT na yau da kullum ba tare da ɗaukar tsangwamar TLS a matsayin gyaran rajista na yau da kullum ba.
Rikodin shop.example:443 ba ya ba Squid hanyar /orders/42. CONNECT yana neman mai masauki/tashar jiragen ruwa; sannan TLS na manufa yana ɗaukar hanyar HTTP a cikin ramin.
| Shaida | Relay na CONNECT na yau da kullum |
|---|---|
| Mai masauki/tashar jiragen ruwa na manufa da sakamakon rami | Akwai ga wakili. |
| Hanyar HTTPS ta ciki da bukatar aikace-aikace | An ɓoye tsakanin abokin ciniki da gidan yanar gizo. |
Yankin URL na mai bincike wanda ke farawa da # | Yawanci yana zama a cikin abokin ciniki, har ma a wajen rajistar wakili. |
Tsarin rajista zai iya rubuta filayen da Squid ke da su, ba zai iya buɗe saƙonnin da ba a gani ba. Aika HTTP na fili ya bambanta domin mai shiga tsakani yana karɓar wannan bukatar HTTP. Fitowa mai cikakken bayani ba ya canza iyakar CONNECT.
Tsangwamar TLS da aka sarrafa tana canza amincewar abokin ciniki da bukatun gudanarwa. Ba ƙaramin maɓallin rajista ba ne kuma ba lallai ba ne ga wakilin gaba na al'ada mai canza IP.
Idan aikace-aikacen naka ne kuma kana buƙatar bincike a matakin shafi, yi amfani da rajistarsa ko kididdigar abokin ciniki da aka tsara yadda ya kamata. Don gazawar wakili, riƙe mai masaukin manufa, lokaci, matsayi da matakin haɗin da aka kammala; sau da yawa suna gano matsalar ba tare da tattara hanyoyin shafi na sirri ba.