{"id":56128,"date":"2020-02-05T00:00:00","date_gmt":"2020-02-04T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/reliz-chrome-80"},"modified":"2020-02-18T14:04:20","modified_gmt":"2020-02-18T11:04:20","slug":"reliz-chrome-80","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/news\/reliz-chrome-80","title":{"rendered":"Lansarea Chrome 80","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Compania Google <noindex><a rel=\"nofollow\" href=\"https:\/\/chromereleases.googleblog.com\/2020\/02\/stable-channel-update-for-desktop.html\">a prezentat<\/a><\/noindex> lansarea unui browser web <noindex><a rel=\"nofollow\" href=\"http:\/\/www.google.com\/chrome\">Chrome 80<\/a><\/noindex>. \u00cen acela\u0219i timp <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromium.org\/developers\/calendar\">disponibil<\/a><\/noindex> versiunea stabil\u0103 a unui proiect open-source <noindex><a rel=\"nofollow\" href=\"http:\/\/dev.chromium.org\/\">Chromium<\/a><\/noindex>, care st\u0103 la baza Chrome. Browserul Chrome <noindex><a rel=\"nofollow\" href=\"https:\/\/code.google.com\/p\/chromium\/wiki\/ChromiumBrowserVsGoogleChrome\">se distinge<\/a><\/noindex> utilizarea logo-urilor Google, existen\u021ba unui sistem de trimitere a notific\u0103rilor \u00een caz de crash, posibilitatea de a \u00eenc\u0103rca modulul Flash la cerere, module pentru redarea con\u021binutului video protejat (DRM), un sistem de instalare automat\u0103 a actualiz\u0103rilor \u0219i transmiterea \u00een timpul c\u0103ut\u0103rii <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=26822\">parametrii RLZ<\/a><\/noindex>. Urm\u0103toarea versiune Chrome 81 este programat\u0103 pentru 17 martie.<\/p>\n<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/chrome\/a\/answer\/7679408\">Principalele<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/productforums.google.com\/forum\/#!forum\/chrome\">modific\u0103ri<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2019\/12\/chrome-80-content-indexing-es-modules.html\">\u00een<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2020\/\">Chrome<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/blog\/v8-release-80\">80<\/a><\/noindex>:\n<\/p>\n<ul>\n<li class=\"l\"> Pentru un mic procent de utilizatori, a fost introdus\u0103 func\u021bia de grupare a tab-urilor, care permite combinarea mai multor tab-uri similare \u00eentr-un grup vizual separat. Fiecare grup poate avea o culoare \u0219i un nume propriu. Utilizatorii care nu au fost inclu\u0219i \u00een prima rund\u0103 de activare pot activa suportul pentru grupare prin op\u021biunea chrome:\/\/flags\/#tab-groups.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/pics_base\/0_1580888736.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/beb1532c92889a0623d9b36fbbd11dff.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> A fost ad\u0103ugat suport pentru func\u021bia <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=50156\">Scroll-To-Text<\/a><\/noindex>, care permite crearea de linkuri pentru cuvinte sau fraze separate, f\u0103r\u0103 a indica explicit \u00een document etichete folosind tag-ul <a name> sau proprietatea . Sintaxa acestor linkuri este planificat\u0103 pentru a fi aprobat\u0103 ca standard web, care se afl\u0103 deocamdat\u0103 \u00een stadiul <noindex><a rel=\"nofollow\" href=\"https:\/\/wicg.github.io\/ScrollToTextFragment\/\">brouillon<\/a><\/noindex>. Masca pentru navigare (care, de fapt, efectueaz\u0103 o c\u0103utare cu derulare) se separ\u0103 de un ancoraj obi\u0219nuit prin caracterul \":~:\". De exemplu, c\u00e2nd deschide\u021bi linkul \"https:\/\/opennet.ru\/52312\/#:~:text=Chrom\u0435\", pagina se va muta la prima men\u021biune a cuv\u00e2ntului \"Chrom\u0435\" \u0219i acest cuv\u00e2nt va fi eviden\u021biat.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/02\/samesite-cookie-changes-in-february.html\">Aplicat<\/a><\/noindex> o restric\u021bie mai sever\u0103 a transferului de Cookie \u00eentre site-uri, pentru solicit\u0103rile non-HTTPS, interzic\u00e2nd prelucrarea Cookie-urilor ter\u021be emise atunci c\u00e2nd se acceseaz\u0103 site-uri diferite de domeniul paginii curente. Astfel de Cookie-uri sunt utilizate pentru a urm\u0103ri mi\u0219c\u0103rile utilizatorului \u00eentre site-uri \u00een codul re\u021belelor publicitare, widget-uri ale re\u021belelor sociale \u0219i sisteme de web-analiz\u0103. Reamintim c\u0103 pentru gestionarea transferului de Cookie se aplic\u0103 atributul SameSite, specificat \u00een header-ul Set-Cookie, care acum, \u00een mod implicit, este setat la \"SameSite=Lax\", limit\u00e2nd trimiterea de Cookie-uri pentru sub-solicit\u0103rile \u00eentre site-uri, cum ar fi cererile de imagini sau \u00eenc\u0103rcarea de con\u021binut prin iframe de pe un alt site. Site-urile pot suprascrie modul implicit de SameSite, specific\u00e2nd \u00een mod explicit valoarea SameSite=None la setarea Cookie-urilor. Totu\u0219i, valoarea SameSite=None pentru Cookie poate fi setat\u0103 doar \u00een modul Secure (valabil pentru conexiunile prin HTTPS). Modificarea va \u00eencepe treptat <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromium.org\/updates\/same-site\">fi utilizat<\/a><\/noindex> 17 februarie, ini\u021bial pentru un mic procent de utilizatori, iar apoi extinz\u00e2nd treptat acoperirea.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52158\">Ad\u0103ugat<\/a><\/noindex> protec\u021bia \u00eempotriva notific\u0103rilor enervante legate de confirmarea permisiunilor. Deoarece o astfel de activitate, cum ar fi spamul cu solicit\u0103ri pentru primirea de notific\u0103ri push, \u00eentrerupe activitatea utilizatorului \u0219i distrage aten\u021bia de la ac\u021biunile din dialogurile de confirmare, \u00een Chrome 80, \u00een locul unui dialog separat, acum poate ap\u0103rea un mesaj informativ \u00een bara de adrese cu un avertisment despre blocarea solicit\u0103rii de permisiuni, care se contract\u0103 apoi \u00eentr-un indicator cu un clopot t\u0103iat. Prin clic pe indicator, se poate activa sau respinge permisiunea solicitat\u0103 \u00een orice moment convenabil. Automat, noul mod va fi activat selectiv pentru utilizatorii care, p\u00e2n\u0103 acum, blocau \u00een mod obi\u0219nuit aceste solicit\u0103ri, precum \u0219i pentru site-urile pe care se \u00eenregistreaz\u0103 un procent mare de respingere a solicit\u0103rilor. Pentru a activa noul mod pentru toate solicit\u0103rile, \u00een set\u0103ri a fost ad\u0103ugat\u0103 o op\u021biune special\u0103 (chrome:\/\/flags\/#quiet-notification-prompts).\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/pics_base\/0_1578565088.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/0417193e7ff32c39042da014436c1d3a.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2019\/12\/chrome-80-deps-rems\">A fost interzis<\/a><\/noindex> afi\u0219area ferestrelor pop-up (apelul metodei window.open()) \u0219i trimiterea de solicit\u0103ri sincrone XMLHttpRequest \u00een handlerii evenimentelor de \u00eenchidere sau ascundere a paginii (unload, beforeunload, pagehide \u0219i visibilitychange);\n<li class=\"l\"> S-a propus o ini\u021biere <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=51612\">protec\u021biei<\/a><\/noindex> de la \u00eenc\u0103rcarea de con\u021binut multimedia mixt (c\u00e2nd pe o pagin\u0103 HTTPS se \u00eencarc\u0103 resurse prin protocolul http:\/\/). Pe paginile deschise prin HTTPS, linkurile \u201ehttp:\/\/\u201d vor fi acum \u00eenlocuite automat cu \u201ehttps:\/\/\u201d \u00een blocurile legate de redarea fi\u0219ierelor audio \u0219i video. Dac\u0103 un resource audio sau video nu este disponibil prin https, atunci desc\u0103rcarea sa va fi blocat\u0103 (poate fi marcat\u0103 manual pentru deblocare prin meniul accesibil prin simbolul lac\u0103tului din bara de adrese).\n<p>Imaginile vor continua s\u0103 se \u00eencarce f\u0103r\u0103 modific\u0103ri (\u00eenlocuirea automat\u0103 va fi aplicat\u0103 \u00een Chrome 81), dar pentru \u00eenlocuirea pe https sau blocarea imaginilor, dezvoltatorilor de site-uri li se ofer\u0103 propriet\u0103\u021bile CSP upgrade-insecure-requests \u0219i block-all-mixed-content. Pentru scripturi \u0219i iframe, blocarea con\u021binutului mixt a fost implementat\u0103 anterior.<\/p>\n<li class=\"l\"> A \u00eenceput treptat <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=51295\">dezactivarea<\/a><\/noindex> suportului FTP. Implicit, suportul FTP este \u00eenc\u0103 men\u021binut, dar va fi <noindex><a rel=\"nofollow\" href=\"https:\/\/chromestatus.com\/feature\/6246151319715840\">efectuat<\/a><\/noindex> un experiment, \u00een cadrul c\u0103ruia suportul FTP va fi dezactivat pentru un anumit procent de utilizatori (pentru a reveni, va trebui s\u0103 porni\u021bi browserul cu op\u021biunea \u201e--enable-ftp\u201d). Amintim c\u0103 \u00een editiile anterioare a fost deja dezactivat\u0103 afi\u0219area con\u021binutului resurselor \u00eenc\u0103rcate prin protocolul \u201eftp:\/\/\u201d (de exemplu, s-a \u00eencetat afi\u0219area documentelor HTML \u0219i a fi\u0219ierelor README), s-a interzis utilizarea FTP-ului pentru \u00eenc\u0103rcarea subresurselor din documente \u0219i s-a \u00eencetat suportul pentru proxy-uri pentru FTP. Cu toate acestea, p\u00e2n\u0103 acum exista posibilitatea de a \u00eenc\u0103rca fi\u0219iere prin linkuri directe \u0219i de a afi\u0219a con\u021binutul directoarelor.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5180316371124224\">Ad\u0103ugat<\/a><\/noindex><br \/>\nposibilitatea utiliz\u0103rii imaginilor vectoriale SVG ca favicon pentru site.<\/p>\n<li class=\"l\"> \u00cen set\u0103ri a fost ad\u0103ugat\u0103 op\u021biunea de a dezactiva selectiv anumite tipuri de date transmise \u00een timpul sincroniz\u0103rii \u00eentre browsere.\n<li class=\"l\"> Pentru utilizatorii corporativi administra\u021bi centralizat a fost ad\u0103ugat un regulament <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/docs\/chrome-enterprise\/policies\/?policy=BlockExternalExtensions\">BlockExternalExtensions<\/a><\/noindex>, care permite interzicerea instal\u0103rii extensiilor externe pe dispozitiv.\n<li class=\"l\"> Implementat\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/features\/optional-chaining\">posibilitatea<\/a><\/noindex> o verificare unic\u0103 a \u00eentregii serii de propriet\u0103\u021bi sau apeluri \u00een JavaScript. De exemplu, atunci c\u00e2nd se accesa \u201edb.user.name.length\u201d, era necesar s\u0103 se verifice treptat defini\u021bia tuturor componentelor, de exemplu, prin \u201eif (db &amp;&amp; db.user &amp;&amp; db.user.name)\u201d. Acum, folosind opera\u021bia \u201e?.\u201d, se poate accesa valoarea \u201edb?.user?.name?.length\u201d f\u0103r\u0103 verific\u0103ri prealabile, iar aceast\u0103 accesare nu va duce la afi\u0219area unei erori. \u00cen caz de probleme (dac\u0103 un element este tratat ca null sau undefined), rezultatul va fi \u201eundefined\u201d.\n<li class=\"l\"> \u00cen JavaScript a fost propus un nou operator logic de unire \u201e<noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/features\/nullish-coalescing\">??<\/a><\/noindex>\u201e, care returneaz\u0103 operanda din dreapta, dac\u0103 operanda din st\u00e2nga are valoarea NULL sau undefined, \u0219i invers. De exemplu, \u201econst foo = bar ?? 'default string'\u201d dac\u0103 bar este null, va returna stringul sau valoarea bar \u00een celelalte cazuri, inclusiv atunci c\u00e2nd bar este 0 \u0219i ' ', spre deosebire de operatorul \u201e||\u201d.\n<li class=\"l\"> \u00cen modul Origin Trials (func\u021bionalit\u0103\u021bi experimentale care necesit\u0103 o activare separat\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.chrome.com\/origintrials\/#\/trials\/active\">activare<\/a><\/noindex>) a fost propus API-ul de indexare a con\u021binutului. Origin Trial implic\u0103 posibilitatea de a lucra cu API-ul specificat din aplica\u021bii, \u00eenc\u0103rcate de pe localhost sau 127.0.0.1, sau dup\u0103 ce s-a finalizat \u00eenregistrarea \u0219i s-a ob\u021binut un token special, care are o valabilitate limitat\u0103 pentru un anumit site. API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/content-indexing-api\/\">Indexarea con\u021binutului<\/a><\/noindex>, oferind metadate despre con\u021binutul care a fost anterior \u00een cache de aplica\u021biile web care func\u021bioneaz\u0103 \u00een modul Progressive Web Apps (PWS). Aplica\u021bia poate salva \u00een browser diverse date, inclusiv imagini, videoclipuri \u0219i articole, iar \u00een cazul pierderii conexiunii la re\u021bea, poate folosi aceste date prin API Cache Storage \u0219i IndexedDB. Content Indexing API permite ad\u0103ugarea, g\u0103sirea \u0219i \u0219tergerea unor astfel de resurse. Acest API este deja folosit \u00een browser pentru a lista paginile \u0219i datele multimedia disponibile pentru vizualizare offline.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/lh5.googleusercontent.com\/tkanWDKiU0jTm_ovD1MMjiV9cMX_XPexDY5_kyiZwScsnlPblj-wZUfWOax8aBAuzY3xl7h8tS4x92npA8UDJiKXH7jJfXTnehfU-g08RPbDZS8I-T62Dqzkrc5-3vN-UzCsXgAg\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/5a9d7a4d4664a7d9e297ca707479d045.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> Interfa\u021ba de programare a aplica\u021biilor <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/contact-picker\/\">Contact Picker<\/a><\/noindex>, permi\u021b\u00e2nd utilizatorului s\u0103 selecteze \u00eenregistr\u0103ri din agenda de contacte \u0219i s\u0103 trimit\u0103 anumite detalii despre acestea c\u0103tre site. La solicitare, se define\u0219te o list\u0103 de propriet\u0103\u021bi care trebuie ob\u021binute. Aceste propriet\u0103\u021bi sunt afi\u0219ate clar utilizatorului, care decide dac\u0103 s\u0103 transmit\u0103 sau nu aceste propriet\u0103\u021bi. API-ul poate fi folosit, de exemplu, \u00eentr-un client de email web pentru a selecta destinatarii unui mesaj, \u00eentr-o aplica\u021bie web cu func\u021bia VoIP pentru a ini\u021bia un apel la un anumit num\u0103r sau \u00eentr-o re\u021bea social\u0103 pentru a c\u0103uta prieteni deja \u00eenregistra\u021bi. \u00cen cadrul Origin Trials, au fost propuse unele propriet\u0103\u021bi noi pentru Contact Picker: pe l\u00e2ng\u0103 nume, email \u0219i num\u0103r de telefon, a fost ad\u0103ugat\u0103 posibilitatea de a transmite adresa po\u0219tal\u0103 \u0219i o imagine.\n<li class=\"l\"> \u00cen Web Workers <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/module-workers\/\">sub licen\u021ba MIT. Instrumentul utilizeaz\u0103 metode de \u00eenv\u0103\u021bare automat\u0103, \u00eempreun\u0103 cu analiza static\u0103 \u0219i dinamic\u0103 a codului JavaScript. Se afirm\u0103 c\u0103 utilizarea \u00eenv\u0103\u021b\u0103rii automate a permis \u00eembun\u0103t\u0103\u021birea semnificativ\u0103 a preciziei \u00een identificarea codului pentru identificarea ascuns\u0103 \u0219i a identificat cu 26% mai multe scripturi problematice<\/a><\/noindex> o nou\u0103 metod\u0103 de \u00eenc\u0103rcare a modulelor ECMAScript, care permite evitarea utiliz\u0103rii func\u021biei importScripts(), ce blocheaz\u0103 lucr\u0103torul \u00een timpul proces\u0103rii scriptului importat \u0219i \u00eel execut\u0103 \u00een contextul global. Noua metod\u0103 implic\u0103 crearea de module speciale pentru Web Workers, care sus\u021bin mecanismele standard de import JavaScript \u0219i pot fi \u00eenc\u0103rcate dinamic, f\u0103r\u0103 a bloca execu\u021bia lucr\u0103torului. Pentru \u00eenc\u0103rcarea modulelor, constructorul Worker prevede un nou tip de resurs\u0103 - 'module':\n<p>   const worker = new Worker('worker.js', {<br \/>\n     type: 'module'<br \/>\n   });<\/p>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/chromestatus.com\/feature\/5855937971617792\">Implementat\u0103<\/a><\/noindex> func\u021bionalitate integrat\u0103 de procesare \u00een JavaScript a fluxurilor comprimate, care nu necesit\u0103 utilizarea bibliotecilor externe. Pentru comprimare \u0219i decompresie, au fost ad\u0103ugate API-urile <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/document\/d\/1TovyqqeC3HoO0A4UUBKiCyhZlQSl7jM_F7KbWjK2Gcs\/edit\">CompressionStream \u0219i DecompressionStream<\/a><\/noindex>. Suport\u0103 comprimarea folosind algoritmii gzip \u0219i deflate.\n<p>   const compressionReadableStream<br \/>\n         = inputReadableStream.pipeThrough(new CompressionStream('gzip'));<\/p>\n<li class=\"l\"> A fost ad\u0103ugat proprietatea CSS \u201e<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5668660729348096\">line-break: anywhere<\/a><\/noindex>\u201e, care permite \u00eentreruperi la nivelul oric\u0103rui simbol tipografic, inclusiv \u00eentreruperi l\u00e2ng\u0103 simboluri de punctua\u021bie, spa\u021bii predefinite (<pre>) \u0219i \u00een mijlocul cuvintelor. De asemenea, a fost ad\u0103ugat proprietatea CSS \u201e<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5126089347170304\">overflow-wrap: anywhere<\/a><\/noindex>\u201e care permite ruperea secven\u021belor ne\u00eentrerupte de caractere \u00een orice loc, dac\u0103 nu s-a g\u0103sit o pozi\u021bie adecvat\u0103 pentru \u00eentrerupere \u00een \u0219ir.\n<li class=\"l\"> Pentru un context media, prelucrat \u00een mod criptat, a fost implementat\u0103 suportul pentru metoda <noindex><a rel=\"nofollow\" href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/MediaCapabilities\/decodingInfo\">MediaCapabilities.decodingInfo()<\/a><\/noindex>, care furnizeaz\u0103 informa\u021bii despre capacit\u0103\u021bile browser-ului legate de decodarea con\u021binutului protejat (de exemplu, aceast\u0103 metod\u0103 poate fi utilizat\u0103 pentru a selecta scenarii de decodare de \u00eenalt\u0103 calitate sau economisitoare de energie, av\u00e2nd \u00een vedere l\u0103\u021bimea de band\u0103 disponibil\u0103 \u0219i dimensiunea ecranului).\n<li class=\"l\"> A fost ad\u0103ugat\u0103 metoda <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5687791428042752\">HTMLVideoElement.getVideoPlaybackQuality()<\/a><\/noindex>, prin care se pot ob\u021bine informa\u021bii despre performan\u021ba red\u0103rii videoclipului, pentru ajustarea bitrate-ului, rezolu\u021biei \u0219i altor parametrii video.\n<li class=\"l\"> \u00cen API <noindex><a rel=\"nofollow\" href=\"https:\/\/www.w3.org\/TR\/payment-request\/\">Payment Handler<\/a><\/noindex>, care simplific\u0103 integrarea cu sistemele de plat\u0103 existente, a fost ad\u0103ugat\u0103 posibilitatea <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5660404216758272\">delegarea<\/a><\/noindex> de a transmite adresa \u0219i informa\u021biile de contact unui procesator de pl\u0103\u021bi extern (aplica\u021bia sistemului de plat\u0103 poate avea informa\u021bii mai exacte dec\u00e2t browser-ul).\n<li class=\"l\"> A fost ad\u0103ugat suport pentru header-ul HTTP <noindex><a rel=\"nofollow\" href=\"https:\/\/w3c.github.io\/webappsec-fetch-metadata\/#sec-fetch-dest-header\">Sec-Fetch-Dest<\/a><\/noindex>, care permite trimiterea de metadate suplimentare despre tipul de con\u021binut asociat cererii (de exemplu, pentru cererea prin eticheta img se specific\u0103 tipul \u201eimage\u201d, pentru fonturi - \u201efont\u201d, pentru scripturi - \u201escript\u201d, pentru stiluri - \u201estyle\u201d etc.). Pe baza tipului specificat, serverul poate lua m\u0103suri pentru a se proteja \u00eempotriva unor tipuri de atacuri (de exemplu, este pu\u021bin probabil ca un link c\u0103tre un handler pentru transferul de bani s\u0103 fie specificat prin eticheta img, astfel c\u0103 aceste cereri nu trebuie procesate).\n<li class=\"l\"> \u00cen motorul JavaScript V8 <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/blog\/v8-release-80\">a fost efectuat\u0103 optimizarea<\/a><\/noindex> stoc\u0103rii pointerilor \u00een heap. \u00cen loc de o valoare complet\u0103 de 64 de bi\u021bi, este asigurat\u0103 stocarea doar a bi\u021bilor inferiori unici ai pointerului. Aceast\u0103 optimizare a permis reducerea consumului de memorie \u00een heap cu 40%, \u00een schimbul unei sc\u0103deri a performan\u021bei de 3-8%.<br \/>\n<center><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/f4d864466d5a0deb2b358e3d709d2e6c.png\" style=\"display:block;margin: 0 auto;\" \/><\/center><\/p>\n<p><center><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/5219cc489b9572b105bb1dceeaedde6d.png\" style=\"display:block;margin: 0 auto;\" \/><\/center>\t<\/p>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2019\/12\/devtools\">Modific\u0103ri<\/a><\/noindex> \u00een instrumentele pentru dezvoltatori web:\n<ul>\n<li class=\"l\"> \u00cen consola web a ap\u0103rut posibilitatea de a suprascrie expresiile let \u0219i class.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/letafter.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/900fb4a45dcfbe3c59093a875664d432.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> Instrumentele de depanare pentru WebAssembly au fost \u00eembun\u0103t\u0103\u021bite. A fost ad\u0103ugat suportul pentru  <noindex><a rel=\"nofollow\" href=\"http:\/\/dwarfstd.org\/\">DWARF<\/a><\/noindex> pentru depanarea pas cu pas, definirea punctelor de oprire \u0219i analiza tras\u0103rilor stivei \u00een codul surs\u0103 pe care este scris\u0103 aplica\u021bia WebAssembly.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/wasm.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/18918605318647f5bdaf403822f83010.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> Panoul pentru analiza activit\u0103\u021bii de re\u021bea a fost \u00eembun\u0103t\u0103\u021bit. A fost ad\u0103ugat\u0103 op\u021biunea de a vizualiza lan\u021bul de apeluri de scripturi asociate cu ini\u021bierea cererii.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/initiators.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/1981db2b84541612ec63f54dea90a25d.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<p>S-au ad\u0103ugat coloanele noi Path \u0219i URL, care arat\u0103 calea absolut\u0103 \u0219i URL-ul complet pentru fiecare resurs\u0103 de re\u021bea. A fost asigurat\u0103 eviden\u021bierea cererii selectate \u00een diagrama de revizuire.<\/p>\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/overview.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/e2f07ee205c13a4f10ef9b9e944d8fa8.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> \u00cen tab-ul Condi\u021bii de re\u021bea, a fost ad\u0103ugat\u0103 op\u021biunea de a modifica parametrul User-Agent.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/useragent.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/c605d0146e32813320d6517c55e4efe2.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> A fost propus un nou interfa\u021b\u0103 pentru configurarea panoului de audit.<br \/>\n<center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/start.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/c16f004b56b488f06fe68d27291b1e11.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> \u00cen tab-ul <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/tools\/chrome-devtools\/coverage\">Acoperire<\/a><\/noindex> s-a oferit posibilitatea de a colecta date de acoperire pentru fiecare func\u021bie sau pentru fiecare bloc de cod (statistic\u0103 mai detaliat\u0103, dar necesit\u0103 mai multe resurse).\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/modes.png\"><img decoding=\"async\" alt=\"Lansarea Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/2c80bbceb4c576bf399399986c81bb2d.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<\/ul>\n<li class=\"l\"> Ac\u021biunea manifestului AppCache (tehnologie pentru organizarea func\u021bion\u0103rii aplica\u021biei web \u00een mod offline) <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/01\/appcache-scope-restricted.html\">este limitat\u0103<\/a><\/noindex> la directorul curent al site-ului (dac\u0103 manifestul a fost \u00eenc\u0103rcat de la www.example.com\/foo\/bar\/, posibilitatea de a rescrie URL-ul va func\u021biona doar \u00een interiorul \/foo\/bar\/). \u00cen Chrome 82, suportul pentru AppCache este planificat s\u0103 fie eliminat complet. Motivul invocat este dorin\u021ba de a elimina una dintre vectorii pentru atacurile legate de scripting \u00eentre site-uri. \u00cen loc de AppCache, se recomand\u0103 utilizarea API-ului <noindex><a rel=\"nofollow\" href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/Cache\">Cache<\/a><\/noindex>.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2019\/12\/webvr-1-1-removed\">Oprit<\/a><\/noindex> suportul pentru API-ul \u00eenvechit WebVR 1.1, \u00een locul c\u0103ruia poate fi folosit API-ul <noindex><a rel=\"nofollow\" href=\"https:\/\/immersive-web.github.io\/webxr\/\">WebXR Device<\/a><\/noindex>, care permite accesul la componente pentru crearea unor experien\u021be de realitate virtual\u0103 \u0219i augmentat\u0103 \u0219i unific\u0103 lucrul cu diverse clase de dispozitive, de la c\u0103\u0219ti sta\u021bionare de realitate virtual\u0103 p\u00e2n\u0103 la solu\u021bii bazate pe dispozitive mobile.\n<li class=\"l\"> Handlerii de protocoale, conecta\u021bi prin metodele registerProtocolHandler() \u0219i unregisterProtocolHandler(), acum pot func\u021biona doar \u00een context sigur (prin acces HTTPS).\n<\/ul>\n<p>Pe l\u00e2ng\u0103 nout\u0103\u021bi \u0219i corec\u021bii de erori, noua versiune a eliminat <noindex><a rel=\"nofollow\" href=\"https:\/\/bugs.chromium.org\/p\/chromium\/issues\/list?can=1&#038;q=label%3ARelease-0-M80\">56 de vulnerabilit\u0103\u021bi<\/a><\/noindex>. Multe dintre vulnerabilit\u0103\u021bi au fost descoperite ca urmare a test\u0103rii automate cu instrumentele <noindex><a rel=\"nofollow\" href=\"http:\/\/code.google.com\/p\/address-sanitizer\/wiki\/AddressSanitizer\">AddressSanitizer<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/code.google.com\/p\/memory-sanitizer\/wiki\/MemorySanitizer\">MemorySanitizer<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/sites.google.com\/a\/chromium.org\/dev\/developers\/testing\/control-flow-integrity\">Control Flow Integrity<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/sites.google.com\/a\/chromium.org\/dev\/developers\/testing\/libfuzzer\">LibFuzzer<\/a><\/noindex> \u0219i <noindex><a rel=\"nofollow\" href=\"http:\/\/lcamtuf.coredump.cx\/afl\/\">AFL<\/a><\/noindex>. Nu au fost identificate probleme critice care s\u0103 permit\u0103 ocolirea tuturor nivelurilor de protec\u021bie ale browserului \u0219i executarea codului \u00een sistem dincolo de mediu sandbox. \u00cen cadrul programului de recompensare pentru descoperirea vulnerabilit\u0103\u021bilor pentru versiunea actual\u0103, compania Google a pl\u0103tit 37 de premii \u00een valoare total\u0103 de 48 de mii de dolari (o recompens\u0103 de 10.000 USD, trei recompense de 5.000 USD, trei recompense de 3.000 USD, patru recompense de 2.000 USD, trei recompense de 1.000 USD \u0219i \u0219ase recompense de 500 USD). Sumele a 17 recompense nu au fost \u00eenc\u0103 definite.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"link\"><\/a><\/noindex><\/p>\n<p>Sursa: <a \ncontent=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52312\">opennet.ro<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430 Chrome 80. \u041e\u0434\u043d\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u043e \u0434\u043e\u0441\u0442\u0443\u043f\u0435\u043d \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u043f\u0443\u0441\u043a \u0441\u0432\u043e\u0431\u043e\u0434\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 Chromium, \u0432\u044b\u0441\u0442\u0443\u043f\u0430\u044e\u0449\u0435\u0433\u043e \u043e\u0441\u043d\u043e\u0432\u043e\u0439 Chrome. \u0411\u0440\u0430\u0443\u0437\u0435\u0440 Chrome \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043b\u043e\u0433\u043e\u0442\u0438\u043f\u043e\u0432 Google, \u043d\u0430\u043b\u0438\u0447\u0438\u0435\u043c \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u043e\u0442\u043f\u0440\u0430\u0432\u043a\u0438 \u0443\u0432\u0435\u0434\u043e\u043c\u043b\u0435\u043d\u0438\u0439 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u043a\u0440\u0430\u0445\u0430, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c\u044e \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u043c\u043e\u0434\u0443\u043b\u044f Flash \u043f\u043e \u0437\u0430\u043f\u0440\u043e\u0441\u0443, \u043c\u043e\u0434\u0443\u043b\u044f\u043c\u0438 \u0434\u043b\u044f \u0432\u043e\u0441\u043f\u0440\u043e\u0438\u0437\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0437\u0430\u0449\u0438\u0449\u0451\u043d\u043d\u043e\u0433\u043e \u0432\u0438\u0434\u0435\u043e\u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430 (DRM), \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0438 \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0435\u0439 \u043f\u0440\u0438 \u043f\u043e\u0438\u0441\u043a\u0435 RLZ-\u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u0432. \u0421\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0439 \u0432\u044b\u043f\u0443\u0441\u043a Chrome 81 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-56128","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/news\/reliz-chrome-80\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 Chrome 80 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/news\/reliz-chrome-80\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-02-04T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:04:20+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Lansare Chrome 80 | ProHoster","description":"Compania Google a lansat versiunea web-browser-ului","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/news\/reliz-chrome-80","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 Chrome 80 | ProHoster","og:description":"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430","og:url":"https:\/\/prohoster.info\/ro\/blog\/news\/reliz-chrome-80","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-02-04T21:00:00+00:00","article:modified_time":"2020-02-18T11:04:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"56128","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:30:42","updated":"2022-10-07 18:25:29","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/56128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=56128"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/56128\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=56128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=56128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=56128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}