Idan Jint ya ba da rahoton ɓacewar dnsResolve ko myIpAddress yayin kimanta PAC, lodin ƙarin JavaScript ba lallai ne shine maganin ba. Waɗannan mataimakan PAC na cikin muhallin da aikace-aikacen mai masaukin ke bayarwa.

Kafin kiran FindProxyForURL

Zaɓi saitin mataimakan PAC da ake goyan baya da iyalan adireshi, sannan ka girka waɗannan mataimakan a kan injin. Ka kiyaye yarjejeniyoyinsu: dnsResolve yana ɗaukar sunan mai masauki, myIpAddress ba ya ɗaukar wata hujja kuma yana buƙatar manufar mu'amalar gida, kuma shExpMatch yana amfani da tsarin salo irin na shell. Wani stub da ke mayar da ƙima mai sauƙi na iya zaɓar hanya mara kyau a asirce.

Bayan kammala wannan farkon, babban kiran zai iya zama haka a cikin Jint 4.4.0:

var destination = new Uri(destinationUrl);
engine.Execute(pacSource);
var routeList = engine.Invoke(
    "FindProxyForURL",
    destinationUrl,
    destination.IdnHost
).AsString();

engine shine Jint.Engine da aka saita; pacSource shine shirin PAC da aka samo. destination.IdnHost yana bayar da sunan mai masauki ba tare da tashar jiragen ruwa ko hanya ba. Wannan kiran ba ya samo PAC kuma ba ya buɗe haɗin wakili.

Bayan kiran

Fassara sakamako kamar PROXY proxy.example:8080; DIRECT a matsayin jerin jeri na masu neman hanya da madadin. Aika dukan igiyar a matsayin URL na wakili yana rasa ma'anarta. Ka ware gazawar kimantawa daga bayyanannen sakamakon DIRECT.

Yayin da yake gudana

Saita iyakokin Jint na tsawon lokaci, kalmomi, ƙwaƙwalwa da sokewa, kuma ka fallasa ayyukan mai masaukin da ake buƙata kawai. Iyakance martanin DNS daban: binciken gudanar da JavaScript ba ya sa kiran mai masauki mai toshewa na sabani ya zama mai yiwuwa a katse. Tsara damar shiga inji ko ba da aiki na lokaci ɗaya misalai masu mallaka daban; injuna ba su da aminci don amfani lokaci ɗaya.

Aiwatar da PAC a cikin burauzoci na iya bambanta a faɗaɗɗen mataimaka da bayanan URL da suke bayyanawa, musamman ga HTTPS. Daidaita sakamakon misali ɗaya yana tabbatar da ƙasa da daidaita halin tafiyar da burauza.

Labarai masu alaƙa