Tura zaɓaɓɓun buƙatun HTTP daga Squid zuwa HTTPS

Squid na iya neman burauza ya sake gwada zaɓaɓɓen HTTP URL ta hanyar HTTPS. Dole ne inda ake nufi ya riga ya ba da albarkatun da suka dace ta HTTPS; gudanar da Squid a kan Raspberry Pi ba ya ƙirƙirar wannan ikon a shafin yanar gizo.

Don hanyar url_rewrite_program ta Squid 7, helper na iya mayar da juya hannun abokin ciniki kamar wannan:

OK status=307 url="https://www.example.com/help"

Wannan misali ne guda ɗaya na amsar helper ga buƙatar da ta dace, ba cikakken shirin helper ba. Burauza na karɓar juyawar kuma yana yin sabon buƙata zuwa HTTPS URL. URL da ke wajen manufar haɓakawa na iya samun OK kuma ta kasance ba ta canza ba.

Yi amfani da sanannen jeri na wuraren da ke iya HTTPS kuma ka bincika URL da ke shigowa. Ka kiyaye hanyar da ake nufi da query, ka lissafa tashoshin da aka bayyana, kuma ka bi hanyoyin buƙata da hankali. Maye gurbin kowane prefix na http da ido rufe yana ɗauka cewa kowace asali tana da sabis na HTTPS daidai.

Helper dole ne ya amsa kowace layin shigarwa bisa ga ka'idar sigar Squid da aka shigar. Idan an kunna tashoshin helper na lokaci ɗaya, ka kiyaye mai gane tashar a cikin amsar. Tsohon misalin 301:URL tsirara ba ya musanya da tsarin result-and-key/value na yanzu.

Zaɓi juya hannun abokin ciniki lokacin da burauza ya kamata ya san sabon URL. Amsar rewrite-url a maimakon haka tana neman Squid ya kawo wani URL a bayan ainihin buƙatar abokin ciniki, wanda zai iya barin URL ɗin aikace-aikacen da yanayinsa ba su daidaita ba.

Buƙatar HTTP ta farko ta riga ta isa Squid kafin helper ya iya juya ta. Wannan manufar ba za ta iya kare wannan buƙatar a baya ba. TLS yana farawa a haɗin HTTPS na gaba; ramin CONNECT kawai ba ya ba da wani ɓoyewa.