Shin babban wakilin Squid yana buƙatar tashar ICP?

Sabis ɗinka na sama yana ba da tashar wakili ɗaya ta HTTP. Rubutun cache_peer na Squid yana neman biyu. Ƙarin filin na tambayoyin ajiya ne, ba wata hanyar haɗi ta biyu ta wajibi ba.

cache_peer parent.example parent 8080 0 no-query name=office_parent

A nan 8080 yana ɗaukar buƙatun wakilin HTTP. Sifili yana cika filin tashar tambaya; no-query yana kashe tambayoyin ICP zuwa wannan abokin. Babban ba dole ya aiwatar da ICP ba.

Amma dole ne ya yi magana da ka'idar wakilin HTTP. Idan babban zai zama na jama'a, jerin wakilan HTTP yana ba da 'yan takarar HTTP da za a duba. Tashar SOCKS ba za ta yi aiki a wurinsa ba. Don HTTPS, duba cewa babban yana ba da izinin hanyar CONNECT da ake buƙata; tallafin ICP ba shi da alaƙa.

Ka raba kulawar shiga da manufar tafiyar da hanya. Bayyana wannan abokin ba ya ba abokan ciniki izini kuma ba ya haramta komawa kai tsaye. Ka riƙe ka'idojin http_access, zaɓin abokin da never_direct da suka dace don buƙatun da ake so.

Canza tashar ICP ba zai iya gyara shigar wakili da aka ƙi ko hanyar CONNECT da aka hana ba.