UGoogle uthethelela uthintelo lwe-webRequest API esetyenziswa ngabathinteli bentengiso

Abaphuhlisi besiphequluli seChrome ndizamile thethelela ukuyekwa kwenkxaso yendlela yokuthintela ukusebenza kwe-webRequest API, ekuvumela ukuba utshintshe umxholo ofunyenweyo kwi-fly kwaye isetyenziswe ngokusebenzayo kwizongezo zokuthintela intengiso,
ukukhuselwa kwi-malware, ukukhohlisa, ukuhlola imisebenzi yabasebenzisi, ulawulo lwabazali kunye nemfihlo.

Iinjongo zikaGoogle:

• Imowudi yokuvala i-API WebRequest kukhokelela ekusetyenzisweni okuphezulu kobutyebi.
  Xa usebenzisa le API, isikhangeli siqala sithumela i-add-on yonke idatha equlethwe kwisicelo senethiwekhi, i-add-on ihlalutya kwaye ibuyisela inguqu elungisiweyo yokuqhubela phambili kwi-browser okanye imiba yokuvimbela imiyalelo. Kule meko, ukulibaziseka okuphambili akuveli kwinqanaba lokucubungula i-traffic nge-add-on, kodwa ngenxa yeendleko eziphezulu zokulungelelanisa ukuphunyezwa kwesongezo. Ngokukodwa, ukukhohlisa okunjalo kufuna ukuqaliswa kwenkqubo eyahlukileyo yokuncedisa, kunye nokusetyenziswa kwe-IPC ukusebenzisana nale nkqubo kunye neendlela zokulandelelana kwedatha;

• I-add-on ilawula ngokupheleleyo yonke i-traffic kwizinga eliphantsi, elivula amathuba amaninzi okuxhatshazwa kunye nokuphulwa kobumfihlo. Ngokwezibalo zikaGoogle, i-42% yazo zonke ezongezo ezinobungozi ezichongiweyo zisebenzise i-webRequest API. Kuyaphawulwa ukuba nyanga zonke, iinzame zokubeka i-avareji ye-1800 izongezo ezinobungozi zivaliwe kwikhathalogu ye-Chrome Web Store. Ngelishwa, ukuphonononga akusivumeli ukuba sibambe zonke izongezo ezikhohlakeleyo ngaphandle kokukhetha, ke ukomeleza ukhuseleko, kwagqitywa ekubeni kucuthwe izongezo kwinqanaba le-API. Ingcamango ephambili kukubonelela ngezongezo kunye nokufikelela kuzo zonke izithuthi, kodwa kuphela kwidatha efunekayo ukuphumeza umsebenzi ojoliswe kuyo. Ngokukodwa, ukuvimba umxholo, akuyimfuneko ukunika i-add-on ukufikelela ngokupheleleyo kuyo yonke idatha eyimfihlo yomsebenzisi;
• I-API yesibhengezo esicetywayo declarativeNetRequest inyamekela wonke umsebenzi wokucoca umxholo ophezulu kwaye ufuna kuphela ukongezwa ukulayisha imithetho yokucoca. I-add-on ayikwazi ukuphazamisa i-traffic kunye nedatha yangasese yomsebenzisi ihlala ingabonakali;
• UGoogle wathathela ingqalelo uninzi lwamagqabaza malunga nokungabikho kokusebenza kwe-declarativeNetRequest API kwaye wandise umda kwinani lemithetho yokucoca ukusuka kwi-30 yamawaka ecetywayo ekuqaleni ukuya kubuninzi behlabathi be-150 lamawaka, kwaye wongeze amandla tshintsha kwaye ungeze imigaqo, susa kwaye ubeke endaweni ye-HTTP headers ( Referer, Cookie, Set-Cookie) kunye nesicelo iparameters;
• Kumashishini, kunokwenzeka ukusebenzisa indlela yokuvimbela ukusebenza kwe-webRequest API, ekubeni umgaqo-nkqubo wokusetyenziswa kweezongezo unqunywe ngumlawuli oqondayo iimpawu zesiseko kwaye uyazi ngeengozi. Ngokomzekelo, i-API echaziweyo ingasetyenziselwa kumashishini ukurekhoda ukuhamba kwezithuthi zabasebenzi kunye nokudibanisa neenkqubo zangaphakathi;
• Injongo kaGoogle ayikokujongela phantsi okanye ukucinezela izongezo ezithintela intengiso, kodwa ukunika amandla ukuyilwa kwezithinteli zentengiso ezikhuselekileyo nezinamandla ngakumbi;
• Ukungafuni ukushiya indlela yokuthintela yokusebenza kwe-webRequest API kunye ne-declarativeNetRequest entsha ichazwa ngumnqweno wokukhawulela ukufikelela kwi-add-ons kwidatha eyimfihlo. Ukuba ushiya i-webRequest API njengoko injalo, uninzi lwee-addons aziyi kusebenzisa i-declarativeNetRequest ekhuseleke ngakumbi, kuba xa ukhetha phakathi kokhuseleko kunye nokusebenza, uninzi lwabaphuhlisi bahlala bekhetha ukusebenza.

Izichaso abaphuhlisi izongezo:

• Iqhutywa ngabaphuhlisi abongezo iimvavanyo bonisa impembelelo engabalulekanga ngokubanzi ekusebenzeni kwee-ad blocking add-ons (ngexesha lovavanyo, ukusebenza kwezongezo ezahlukeneyo kwathelekiswa, kodwa ngaphandle kokuthathela ingqalelo umphezulu wenkqubo eyongezelelweyo elungelelanisa ukuphunyezwa kwabaphathi kwindlela yokuthintela. i-webRequest API);
• Akunakwenzeka ukuyeka ngokupheleleyo ukuxhasa i-API esetyenziswa ngokusebenzayo kwii-add-ons. Esikhundleni sokuyisusa, unokongeza imvume eyahlukileyo kwaye ulawule ngokungqongqo ukufaneleka kokusetyenziswa kwayo kwii-add-ons, eziza kusindisa ababhali bezongezo ezininzi ezidumileyo ekusebenzeni ngokutsha kweemveliso zabo kunye nokuphepha ukusika ukusebenza;
• Ukunciphisa iindleko eziphezulu, awukwazi ukucima i-API, kodwa uphinde uyenze ngokusekelwe kwindlela yeSithembiso, efana nokuphunyezwa kwe-webRequest kwiFirefox;
• Enye indlela ecetywayo, i-declarativeNetRequest, ayiquki zonke iimfuno zabaphuhlisi abongezelelweyo kwi-ad blocking kunye nokhuseleko / ubumfihlo, kuba ayinikezeli ulawulo olupheleleyo kwizicelo zenethiwekhi, ayivumeli ukusetyenziswa kwe-algorithms yokucoca isiko, kwaye ayivumeli. ukusetyenziswa kwemithetho enzima ehambelanayo ngokuxhomekeke kwiimeko;
• Ngemeko yangoku ye-declarativeNetRequest API, akunakwenzeka ukuphinda wenze umsebenzi okhoyo we-uBlock Origin kunye ne-Matrix izongezo zingatshintshwanga, kwaye yenza uphuhliso olongezelelweyo lwezibuko le-NoScript ye-Chrome engenanjongo;
• Iinkxalabo malunga nobumfihlo zikude, kuba imowudi yokufunda kuphela, engathinteliyo ye-webRequest API ishiywe endaweni kwaye isavumela ukongezwa okukhohlakeleyo ukulawula yonke i-traffic, kodwa ayiboneleli ngekhono lokuphazamisa kuyo. fly (tshintsha umxholo, beka iintengiso zakho, uqhube abasebenzi basezimayini kwaye uhlalutye imixholo yeefom zegalelo zingasetyenziswa emva kokuba iphepha ligqibile ukulayisha);
• Abaphuhlisi bebhrawuza nesibindi, Opera и Vivaldi, eyakhiwe kwi-injini yeChromium, inenjongo yokushiya inkxaso ye-webRequest imo yokuthintela kwiimveliso zabo.

umthombo: opennet.ru