Dejinta proxy ee NW.js way kala duwan tahay codsiyada Chromium iyo Node
Ku habee xeerarka proxy ee mishiinka webka NW.js si gooni ah uga duwan maktabadaha Node ee isla barnaamijka desktop-ka isticmaalo.
NW.js waxa uu isla daaqad ku rari karaa sawirka DOM oo uu JSON ku heli karaa maktabad Node. Aqoonso wicitaanka abuura codsiga ka hor inta aadan dooran interface proxy.
Jidka mishiinka webka ee la diiwaangeliyay:
nw.App.setProxyConfig('proxy.example:8080', '');
const route = nw.App.getProxyForURL('https://www.example.com/');Doodda koowaad waa xeerka proxy-ga tan labaadna waa URL-ka PAC. Tani waxay u doorataa barta ugu dambeysa ee HTTP ee qorshayaasha loo socdo marka PAC madhan yahay; HTTPS waxay isticmaashaa dariiqa tunnel-ka la taageeray. Tijaabo madax-bannaan oo bogga dadweynaha ah oo aan lahayn xaqiijinta proxy, gelitaan ka socda liiska proxy HTTP ayaa beddeli kara bartaas.
| Abuuraha codsiga | Siyaasadda la baarayo |
|---|---|
| Kheyraadka DOM ama fetch-ka browser-ka | Habeynta proxy ee mishiinka webka NW.js |
| HTTP-ga xudunta Node ama gaadiid uu leeyahay xidhmeyn | Wakiilka ama interface proxy dadweynaha ee macmiilkaas |
getProxyForURL waxay soo celisaa qoraal siyaasad qaab PAC ah oo loogu talagalay rarista DOM, sida PROXY oo leh barta ugu dambeysa ama DIRECT. Ma xaqiijiso in codsi dhamaystiran uu isticmaalay.
Beddelka process.env.http_proxy ma dhigo inay qayb kasta oo fulin ah akhrisato doorsoomaha. Ku calaamadee ogaal-cilmiyeedka magaca abuuraha ama macmiilka iyo natiijadiisa. Isticmaal habeynta dadweynaha ee xidhmadaas halkii aad ka hagaajin lahayd faylalka node_modules ee casriyeyn beddesho. Wicitaannada HTTPS ee xudunta Node ee isticmaala SOCKS, mid ka mid ah interface-yadaas waa wakiil HTTPS oo taageera SOCKS.