Njengengxenye ye-Google Cloud yayo, i-Google inikeza i- Google Translation API ngesakhiwo sezindleko ezisuselwa ekusetshenzisweni. Kukhona futhi i- API engenamibhalo engasetshenziswa ngaphandle kokhiye , kepha enqaba ukusebenza ngemuva kwezicelo ezimbalwa nje. Lapho usebenzisa umsebenzi wokuhumusha iwebhusayithi weGoogle Chrome, kuyabonakala ukuthi amakhasi angahunyushwa ngekhwalithi enhle kakhulu ngaphandle komkhawulo obonakalayo.
Ngokusobala imodeli ye-nmt ethuthukile isivele isetshenziswa lapha. Kepha iyiphi i-Google esebenzisa i-Chrome ngaphakathi ukuhumusha okuqukethwe futhi ingabe le API nayo ingabhekiswa ngqo - noma ngasohlangothini lweseva? Ukuhlaziya ithrafikhi yenethiwekhi, amathuluzi afana neWireshark noma iTelerik Fiddler , nawo angahlaziya ithrafikhi ebethelwe, ayanconywa. Kepha i-Chrome iletha nezicelo ezizithumela ukuhunyushwa kwekhasi mahhala : Zingabukwa kalula kusetshenziswa i- Chrome DevTools:
Uma wenza ukuhumusha, bese ubamba isicelo esibalulekile se-POST ku- https://translate.googleapis.com nge- "Copy> Copy as cURL (bash)" bese usisebenzisa kuthuluzi elifana nePostman , ngokwesibonelo, ungathumela isicelo futhi ngaphandle kwezinkinga:
Incazelo yamapharamitha e-URL nayo isobala kakhulu.:
| Ukhiye | Inani lesibonelo | Incazelo |
| Anno | 3 | Imodi yesichasiselo (ithinta ifomethi yokubuyisa) |
| iklayenti | te_lib | Ulwazi lweklayenti (luyahlukahluka; nge-interface yewebhu ye-Google Translate inani lingu-"webapp"; lithinta ifomethi yokubuyisa kanye nomkhawulo wesilinganiso) |
| ifomethi | html | String format (kubalulekile ekuhumusheni amathegi e-HTML) |
| v | 1.0 | Inombolo yenguqulo ye-Google Translate |
| ukhiye | AIzaSyBOti4mM-6x9WDnZIjIeyEU21OpBXqWBgw | Ukhiye we-API (bona ngezansi) |
| logld | vTE_20200210_00 | Uhlobo lwesivumelwano |
| sl | de | Ulimi lomthombo |
| tl | zu | Ulimi oluqondiwe |
| sp | nmt | Imodeli ye-ML |
| i-tc | 1 | akwaziwa |
| sr | 1 | akwaziwa |
| tk | 709408.812158 | Ithokheni (bheka ngezansi) |
| Imfashini | 1 | akwaziwa |
Ezinye izihloko zezicelo nazo zisethwe - kepha lezi zinganakwa kakhulu. Ngemuva kokukhetha ngesandla wonke amaheda, kufaka phakathi lawo avela kumenzeli womsebenzisi , kutholakala inkinga yokufaka ikhodi lapho kufakwa izinhlamvu ezikhethekile (lapha lapho kuhunyushwa " Sawubona Umhlaba "):
Uma uphinde uvule i-ejenti yomsebenzisi (lokho ngokuvamile akulimazi), i-API iletha izinhlamvu ezifakiwe ze-UTF-8:
Ingabe sesifinyelele umgomo wethu futhi sinalo lonke ulwazi lokusebenzisa le API ngaphandle kwe-Google Chrome? Kodwa-ke, uma ushintsha umucu ukuze uhunyushwe (insimu yedatha q yesicelo se-POST) kusuka, isibonelo, "Hello World" kuya ku-"Hello World ! ", uzothola umlayezo wephutha.:
Manje senza olunye uhumusho lwale ntambo eguquliwe ngaphakathi kwe-Google Chrome sisebenzisa umsebenzi wokuhumusha iwebhusayithi futhi sithole ukuthi, ngaphezu kwepharamitha u-q , ipharamitha u-tk nayo ishintshile (zonke ezinye ipharamitha zihlale zifana).:
Ngokusobala, kuyisibonakaliso esincike entanjeni, ukwakheka kwayo okungelula ukukubona. Lapho uqala ukuhumusha iwebhusayithi, amafayela alandelayo alayishiwe:
- Ifayela le-1 CSS: translateelement.css
- Imidwebo engu- 4: translate_24dp.png (2x), gen204 (2x)
- Amafayela we-2 JS: main_de.js , element_main.js
Amafayela amabili weJavaScript ahlanganisiwe futhi enziwe minified. Amathuluzi afana ne- JS Nice nama- de4js manje ayasisiza ukwenza la mafayili afundeke kakhudlwana. Ukuze uzisombulule bukhoma, sincoma i-Chrome Extension Requestly, elungisa imigqa yamafayela akude endizeni:
Manje sesingasusa iphutha ikhodi (ama- CORES kufanele aqale asebenze kuseva yendawo). Isigaba sekhodi esifanele sokwenza ithokheni sibonakala sifihliwe kulesi sigaba kufayela le- element_main.js:
b7739bf50b2edcf636c43a8f8910def9
Lapha umbhalo hashed ngosizo abanye ukuqhela kancane . Kepha ngeshwa sisaphuthelwa ucezu olulodwa lwephazili: Ngaphezu kwempikiswano a ( okuwumbhalo ozohunyushwa ), enye ingxabano b idluliselwa emsebenzini Bp () - uhlobo lwembewu olubonakala luguquka ngezikhathi ezithile futhi olufaka futhi ugelezela ku-hashing. Kodwa uvelaphi? Uma sifinyelela ocingweni lomsebenzi we- Bp () , sithola isigaba sekhodi esilandelayo:
b7739bf50b2edcf636c43a8f8910def9
Umsebenzi Hq umenyezelwe ngaphambili ngale ndlela elandelayo:
b7739bf50b2edcf636c43a8f8910def9
I-deobfuscater ishiye ukungcola lapha; ngemuva kokufaka esikhundleni i-String.fromCharCode('...') ngezintambo ezifanele, ukususa i -a() engasebenzi, nokuhlanganisa ndawonye izingcingo zomsebenzi [c(), c()] , umphumela uba...:
b7739bf50b2edcf636c43a8f8910def9
Noma kulula:
b7739bf50b2edcf636c43a8f8910def9
Umsebenzi yq ngaphambilini wawuchazwa ngokuthi:
b7739bf50b2edcf636c43a8f8910def9
Imbewu kubukeka sengathi isentweni yomhlaba google.translate._const._ctkk , etholakala ngesikhathi sokusebenza. Kepha kubekephi? Kokunye, ifayela le-JS ebelilayishwe ngaphambilini main_de.js, okungenani liyatholakala ekuqaleni. Sifaka okulandelayo ekuqaleni:
b7739bf50b2edcf636c43a8f8910def9
Ku-console empeleni sithola imbewu yamanje:
Lokhu kushiya iGoogle Chrome uqobo, okusobala ukuthi inikeza imbewu, njengenketho yokugcina. Ngenhlanhla, ikhodi yayo yomthombo (i-Chromium, kufaka phakathi ingxenye ye-Translate) ingumthombo ovulekile ngakho-ke itholakala esidlangalaleni. Thina donsa Igumbi endaweni futhi uthole ucingo ukuze umsebenzi TranslateScript :: GetTranslateScriptURL efayeleni translate_script.cc e yezingxenye / ukuhumusha / umongo / ifolda isiphequluli:
b7739bf50b2edcf636c43a8f8910def9
Ukuhluka nge-URL kuchazwe kanzima kufayela elifanayo:
b7739bf50b2edcf636c43a8f8910def9
Uma manje sihlola ifayili le- element.js ngokuseduze (ngemuva kokulikhipha futhi), sithola okuhleliwe okunzima c._ctkk - into yegoogle.translate nayo isethwe ngokufanele futhi ukulayishwa kwazo zonke izimpahla ezifanele ( esesizitholile phambilini) kuyasuswa:
b7739bf50b2edcf636c43a8f8910def9
Manje ukhiye wepharamitha uhlala usacatshangelwa (ngenani AIzaSyBOti4mM-6x9WDnZIjIeyEU21OpBXqWBgw). Lokho kubonakala kungukhiye we-API ojwayelekile wesiphequluli (ongatholwa kweminye imiphumela ye-Google ). Isethwe ku-Chromium kufayela translate_url_util.cc kuzinto zefolda / translate / core / browser:
b7739bf50b2edcf636c43a8f8910def9
Ukhiye wenziwa kugoogle_apis / google_api_keys.cc kusuka kunani ledummy:
b7739bf50b2edcf636c43a8f8910def9
Kodwa-ke, ukuhlola kukhombisa ukuthi izingcingo ze-API zisebenza kahle ngaphandle kwale pharamitha yokhiye. Ukuhlola nge-API manje kubuyisela ikhodi yesimo engu-200 ezingcingweni eziphumelelayo. Uma kufinyelelwa umkhawulo, ikhodi yesimo engu-411 ibuyiselwa nomyalezo othi " Izicelo ze-POST zidinga i-Content-length header ". Ngakho-ke, kunconywa ukuthi ufake nale header (esethwe ngokuzenzakalelayo njenge- Temporary Header ku-Postman).
Ifomethi yokubuyisa yezintambo ezihunyushiwe ayijwayelekile uma kunemisho eminingana esicelweni esisodwa. Imisho ngayinye iboshwe ngamathegi i- / b-HTML:
Futhi, i-Google Chrome ayithumeli i-HTML yonke ku-API, kepha igcina amanani emfanelo afana ne- href esicelweni (futhi esikhundleni salokho isetha ama-indices ukuze amaki amaki anikezwe ohlangothini lweklayenti kamuva):
Uma uguqula inani leklayenti lokhiye le-POST kusuka ku- te_lib (i-Google Chrome) ku- webapp ( iwebhusayithi ye-Google Translation ), uthola intambo yokugcina ehunyushiwe:
Inkinga ukuthi usemathubeni amaningi okungena kumkhawulo wamanani kune- te_lib (ngokuqhathanisa: nge- webapp lokhu kufinyelelwe ngemuva kwama-chars angama-40,000, nge te_lib akunamkhawulo wokulinganiselwa). Ngakho-ke sidinga ukubhekisisa ukuthi i-Chrome iwudlulisa kanjani umphumela. Sizoyithola lapha ku- element_main.js:
b7739bf50b2edcf636c43a8f8910def9
Uma uthumela yonke ikhodi ye-HTML ku-API, ishiya izimfanelo empendulweni ehunyushiwe. Ngakho-ke akudingekile ukuba silingise yonke indlela yokuziphatha yokuhlaziya, kodwa sikhiphe iyunithi yezinhlamvu yokugcina, ehunyushiwe empendulweni. Ukuze senze lokhu, sakha umhlaseli wethegi ye-HTML encane elahla omaka be-<i> abangaphandle kakhulu okuhlanganisa nokuqukethwe kwabo futhi isuse omaka be-<b> abangaphandle kakhulu. Ngalolu lwazi singakwazi manje (ngemuva kokufaka ukuncika nomqambi kudinga i-fzaninotto / faker vielhuber / stringhelper ) ukwakha inguqulo ye-server-side ye-API yokuhumusha:
b7739bf50b2edcf636c43a8f8910def9
Okulandelayo imiphumela yokuhlolwa kokuqala okwenziwe ezinhlelweni ezinhlanu ezihlukene ezinama-bandwidth ahlukene namakheli e-IP:
| Uhlamvu | Izinhlamvu ngesicelo ngasinye | Isikhathi | Isilinganiso sephutha | Izindleko nge-API esemthethweni |
| 13.064.662 | ~250 | 03: 36: 17h | 0% | 237,78€ |
| 24.530.510 | ~250 | 11: 09: 13h | 0% | 446,46€ |
| 49.060.211 | ~250 | 20: 39: 10h | 0% | 892,90€ |
| 99.074.487 | ~1000 | 61: 24: 37h | 0% | 1803,16€ |
| 99.072.896 | ~1000 | 62: 22: 20h | 0% | 1803,13€ |
| 4284.802.766 | ~ Ø550 | 159: 11: 37h | 0% | 51 € 5183.41 |
Qaphela: Lokhu okuthunyelwe kwebhulogi kufaka phakathi yonke imibhalo kubhalelwe izinjongo zokuhlola kuphela. Ungayisebenzisi scripts ukusetshenziswa ekhiqizayo, esikhundleni sisebenze esemthethweni kwe-Google-API .