{"id":52639,"date":"2019-11-13T00:00:00","date_gmt":"2019-11-12T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/domen-fronting-na-baze-tls-1-3"},"modified":"2026-05-20T19:54:20","modified_gmt":"2026-05-20T17:54:20","slug":"domen-fronting-na-baze-tls-1-3","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/domen-fronting-na-baze-tls-1-3","title":{"rendered":"Domen-frontend na temelju TLS 1.3","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Uvod<\/h3>\n

\"Domen-frontend
\nModerne korporativne sisteme filtriranja sadr\u017eaja, od renomiranih proizvo\u0111a\u010da poput Cisco, BlueCoat, FireEye, povezuje mnogo sli\u010dnosti sa mo\u0107nijim srodnicima \u2014 DPI sistemima, koji se intenzivno implementiraju na nacionalnom nivou. Su\u0161tina rada i jednih i drugih le\u017ei u pregledu ulaznog i izlaznog internet prometa i, na osnovu crnih\/bijelih lista, donosi odluku o zabrani internet veze. Budu\u0107i da se oboje oslanjaju na sli\u010dne principe, i na\u010dini za zaobila\u017eenje ovih prepreka \u0107e tako\u0111er imati mnogo zajedni\u010dkog.<\/p>\n

Jedna od tehnologija koja omogu\u0107ava efikasno zaobila\u017eenje i DPI-a i korporativnih sistema je domen-frontalizacija. Njena su\u0161tina je u tome \u0161to se pristupa blokiranoj resursi, skrivaju\u0107i se iza drugog, javnog domena, s dobrom reputacijom, koji unaprijed ne\u0107e biti blokiran od strane nijednog sistema, na primjer google.com.<\/p>\n

O ovoj tehnologiji je ve\u0107 napisano mnogo \u010dlanaka i navedeno mnogo primera. Me\u0111utim, popularne i u poslednje vreme raspravljane tehnologije DNS-over-HTTPS i encrypted-SNI, kao i nova verzija protokola TLS 1.3, pru\u017eaju mogu\u0107nost razmatranja jo\u0161 jedne varijante domen-frontalizacije.
\n<\/a><\/p>\n

Istra\u017eujemo tehnologiju<\/h3>\n

Prvo, malo \u0107emo definisati osnovne pojmove, kako bismo svi imali razumevanje ko je ko i za\u0161to je sve to potrebno. Pomenuli smo mehanizam eSNI, \u010diji \u0107e rad biti detaljnije obja\u0161njen. Mehanizam eSNI (encrypted Server Name Indication) \u2014 za\u0161ti\u0107ena verzija SNI, dostupna samo za protokol TLS 1.3. Osnovna su\u0161tina je da \u0161ifruje, izme\u0111u ostalog, informacije o tome kojem domenu se \u0161alje zahtev.<\/p>\n

A sada \u0107emo razmotriti rad mehanizma eSNI u praksi.<\/p>\n

Pretpostavimo da imamo internet resurs koji je blokiran savremenim DPI re\u0161enjem (uzmimo za primer, poznati torrent tracker \u2014 rutracker.nl). Kada poku\u0161amo da pristupimo sajtu torrent trackera \u2014 vidimo standardnu blokadu provajdera da je resurs blokiran:<\/p>\n

\"Domen-frontend<\/p>\n

Na sajtu RKN ovaj domen zaista se nalazi na listama zabrana:<\/p>\n

\"Domen-frontend<\/p>\n

Pri zahtevu whois \u2014 vidi se da je sam domen 'sakriven' iza cloud provajdera Cloudflare.<\/p>\n

\"Domen-frontend<\/p>\n

Ali za razliku od \"stru\u010dnjaka\" iz RKN-a, tehni\u010dki potkovaniji zaposlenici iz Beline (ili pou\u010deni gorkim iskustvom na\u0161eg poznatog regulatora) nisu jednostavno blokirali web stranicu prema IP adresi, ve\u0107 su stavili na crnu listu upravo domen<\/a>. To se lako mo\u017ee provjeriti ako pogledate koji se drugi domene skrivaju iza ovog istog IP adresu<\/a>, posjetite jednu od njih i vidite da pristup nije blokiran:<\/p>\n

\"Domen-frontend<\/p>\n

Kako to mo\u017ee biti? Kako provajderski DPI saznaje na koji od domena odlazi moj preglednik, budu\u0107i da se sve komunikacije odvijaju putem protokola https, a ne primje\u0107ujemo da Belin manipulira https certifikatima? Je li on vidovnjak ili me netko prati?<\/p>\n

Poku\u0161ajmo odgovoriti na ovo pitanje, pogledav\u0161i promet kroz Wireshark.<\/p>\n

\"Domen-frontend<\/p>\n

Na snimci ekrana vidimo da pregleda\u010d prvo dobiva IP adresu servera preko DNS-a, zatim dolazi do standardnog TCP rukovanja s odredi\u0161nim serverom, a nakon toga preglednik poku\u0161ava uspostaviti ssl vezu sa serverom. Da bi to u\u010dinio, \u0161alje paket SSL<\/a> Client Hello, u kojem se nalazi naziv izvorne domene u otvorenom obliku. Ovo polje je potrebno frontend serveru cloudflare kako bi ispravno usmjerio vezu. Tu nas hvata provajderski DPI, prekinuv\u0161i na\u0161u vezu. Pri tome ne primamo nikakvu obavijest od provajdera, te vidimo standardnu pogre\u0161ku preglednika kao da je stranica isklju\u010dena ili jednostavno ne radi:<\/p>\n

\"Domen-frontend<\/p>\n

Sada uklju\u010dimo mehanizam eSNI u pregledniku, kako je opisano u uputama za Firefox <\/a>:
\nZato otvaramo stranicu konfiguracije Firefoxa about:config<\/b> i aktiviramo sljede\u0107e postavke:<\/p>\n

network.trr.mode = 2;\nnetwork.trr.uri = https:\/\/mozilla.cloudflare-dns.com\/dns-query\nnetwork.security.esni.enabled = true\n<\/code><\/pre>\n
Nakon toga \u0107emo provjeriti ispravnost rada postavki na web stranici cloudflare putem vezi<\/a> i poku\u0161ati trik s na\u0161im torrent trackerom jo\u0161 jednom.<\/p>\n
\"Domen-frontend<\/p>\n
Evo ga. Na\u0161 omiljeni tracker se otvorio, bez ikakvih VPN-a i proxy servera. Sada pogledajmo dump prometa u Wiresharku, \u0161to se dogodilo.<\/p>\n
\"Domen-frontend<\/p>\n
Ovaj put paket ssl client hello ne sadr\u017ei izravno odredi\u0161nu domenu, ve\u0107 se u paketu pojavilo novo polje \u2014 encrypted_server_name \u2014 upravo tamo se nalazi vrijednost rutracker.nl, a to polje mo\u017ee de\u0161ifrirati samo frontend server cloudflare. Ako je tako, provajderski DPI nema nikakvu drugu mogu\u0107nost nego oprati ruke i dopustiti takav promet. A nema drugih opcija s enkripcijom.<\/p>\n
Dakle, kako tehnologija funkcioni\u0161e u pretra\u017eiva\u010du \u2014 to smo istra\u017eili. Sada hajde da poku\u0161amo da je primenimo na konkretnije i zanimljivije stvari. Za po\u010detak, nau\u010di\u0107emo kako koristiti curl uz eSNI za rad sa TLS 1.3, a istovremeno \u0107emo videti kako funkcioni\u0161e sam domen-fronting zasnovan na eSNI.<\/p>\n
Domen-fronting sa eSNI<\/h3>\n
S obzirom na to da curl za povezivanje preko https protokola koristi standardnu openssl biblioteku, pre svega, potrebno je osigurati podr\u0161ku za eSNI upravo tamo. U master granama openssl jo\u0161 uvek nema podr\u0161ke za eSNI, pa \u0107emo morati preuzeti posebnu gran\u0443 openssl, da je iskompajliramo i instaliramo.<\/p>\n
Kloni\u0107emo repozitorijum sa GitHub-a i kompajlirati kao i obi\u010dno:<\/p>\n
$ git clone https:\/\/github.com\/sftcd\/openssl\n$ cd openssl\n$ .\/config\n\n$ make\n$ cd esnistuff\n$ make\n<\/code><\/pre>\n
Zatim \u2014 kloniramo repozitorijum sa curl-a i konfiguri\u0161emo njegovu kompilaciju koriste\u0107i na\u0161u sakupljenu openssl biblioteku:<\/p>\n
$ cd $HOME\/code\n$ git clone https:\/\/github.com\/niallor\/curl.git curl-esni\n$ cd curl-esni\n\n$ export LD_LIBRARY_PATH=\/opt\/openssl\n$ .\/buildconf\n$ LDFLAGS=\"-L\/opt\/openssl\" .\/configure --with-ssl=\/opt\/openssl --enable-esni --enable-debug\n<\/code><\/pre>\n
Ovde je va\u017eno pravilno navesti sve direktorijume u kojima se nalazi openssl (u na\u0161em slu\u010daju \u2014 to je \/opt\/openssl\/) i osigurati da proces konfiguracije pro\u0111e bez gre\u0161aka.<\/p>\n
U slu\u010daju uspe\u0161ne konfiguracije \u2014 vide\u0107emo red:<\/p>\n
WARNING: esni ESNI enabled but marked EXPERIMENTAL. Use with caution!<\/b><\/p>\n
$ make<\/code><\/pre>\n
Nakon uspe\u0161ne izrade paketa iskoristi\u0107emo poseban bash fajl iz sastava openssl za pode\u0161avanje i pokretanje curl-a. Kopira\u0107emo ga u direktorijum sa curl-om radi lak\u0161e upotrebe:<\/p>\n
cp \/opt\/openssl\/esnistuff\/curl-esni <\/code><\/pre>\n
i izvr\u0161i\u0107emo testni https zahteva na cloudflare server, istovremeno bele\u017ee\u0107i DNS i TLS pakete u Wireshark-u.<\/p>\n
$ ESNI_COVER=\"www.hello-rkn.ru\" .\/curl-esni https:\/\/cloudflare.com\/<\/code><\/pre>\n
U odgovoru servera, pored mno\u0161tva informacija za debagovanje od openssl i curl-a, dobi\u0107emo HTTP odgovor sa kodom 301 od cloudflare.<\/p>\n
HTTP\/1.1 301 Moved Permanently\n< Date: Sun, 03 Nov 2019 13:12:55 GMT\n< Transfer-Encoding: chunked\n< Connection: keep-alive\n< Cache-Control: max-age=3600\n< Expires: Sun, 03 Nov 2019 14:12:55 GMT\n< Location: https:\/\/www.cloudflare.com\/\n<\/code><\/pre>\n
\u0161to ukazuje na to da je na\u0161 zahtev uspe\u0161no dostavljen do odredi\u0161nog servera, \u010duo i obra\u0111en.<\/p>\n
Sada hajde da pogledamo snimak saobra\u0107aja u Wireshark-u, tj. \u0161ta je u ovom slu\u010daju video providerov DPI.<\/p>\n
\"Domen-frontend<\/p>\n
Vidljivo je da je prvo curl kontaktirao DNS poslu\u017eitelj za javnim eSNI klju\u010dem za cloudflare poslu\u017eitelj \u2014 TXT DNS upit na _esni.cloudflare.com (paket br. 13). Zatim, koriste\u0107i openssl biblioteku, curl je poslao TLS 1.3 upit na cloudflare poslu\u017eitelj u kojem je SNI polje bilo \u0161ifrirano javnim klju\u010dem dobivenim u prethodnoj fazi (paket br. 22). Me\u0111utim, osim eSNI polja, u SSL-hello paketu umetnuto je i polje s obi\u010dnim \u2014 otvorenim SNI, koje mo\u017eemo odrediti u proizvoljnom redoslijedu (u ovom slu\u010daju \u2014 www.hello-rkn.ru<\/a>). <\/b><\/p>\n
Ovo polje otvorenog SNI nije se uzimalo u obzir prilikom obrade od strane cloudflare poslu\u017eitelja i samo je slu\u017eilo kao maskiranje za DPI pru\u017eatelja usluga. Cloudflare poslu\u017eitelj je prihvatio na\u0161 ssl-hello paket, de\u0161ifrirao eSNI, izvukao iz njega originalni SNI i obradio ga kao da se ni\u0161ta nije dogodilo (u\u010dinio je sve upravo onako kako je planirano tijekom razvoja eSNI).<\/p>\n
Jedina stvar na koju se mo\u017ee obratiti pa\u017enja s aspekta DPI-a je prvotni DNS upit na _esni.cloudflare.com. No, u\u010dinili smo DNS upit otvorenim samo kako bismo pokazali kako ovaj mehanizam radi iznutra.<\/p>\n
Da bismo kona\u010dno sru\u0161ili temelje DPI-a, koristimo ve\u0107 spomenuti mehanizam DNS-over-HTTPS. Mali podsjetnik \u2013 DOH \u2013 protokol koji omogu\u0107uje za\u0161titu od napada \"\u010dovjeka u sredini\" slanjem DNS upita preko HTTPS protokola.<\/p>\n
Ponovit \u0107emo upit, ali ovaj put javne eSNI klju\u010deve dobit \u0107emo putem https protokola, a ne DNS-a:<\/p>\n
ESNI_COVER=\"www.hello-rkn.ru\" DOH_URL=https:\/\/mozilla.cloudflare-dns.com\/dns-query .\/curl-esni https:\/\/cloudflare.com\/<\/code><\/pre>\n
Damp prometa upita prikazan je na slici ispod:<\/p>\n
\"Domen-frontend<\/p>\n
Vidljivo je da prvo curl pristupa poslu\u017eitelju mozilla.cloudflare-dns.com putem DoH protokola (https veza na poslu\u017eitelj 104.16.249.249) kako bi od njih dobio vrijednosti javnih klju\u010deva za \u0161ifriranje SNI, a zatim se povezuje s odredi\u0161nim poslu\u017eiteljem, skrivaju\u0107i se pritom iza domene www.hello-rkn.ru<\/a>.<\/p>\n
Osim gore navedenog DoH resolvera mozilla.cloudflare-dns.com, mo\u017eemo koristiti i druge popularne DoH usluge, na primjer, iz poznate zle korporacije.
\nIzvr\u0161imo takav zahtjev:<\/p>\n
ESNI_COVER=\"www.kremlin.ru\" DOH_URL=https:\/\/dns.google\/dns-query .\/curl-esni https:\/\/rutracker.nl\/<\/code><\/pre>\n
I dobit \u0107emo odgovor:<\/p>\n
< HTTP\/1.1 301 Moved Permanently\n< Date: Sun, 03 Nov 2019 14:10:22 GMT\n< Content-Type: text\/html\n< Transfer-Encoding: chunked\n< Connection: keep-alive\n< Set-Cookie: __cfduid=da0144d982437e77b0b37af7d00438b1a1572790222; expires=Mon, 02-Nov-20 14:10:22 GMT; path=\/; domain=.rutracker.nl; HttpOnly; Secure\n< Location: https:\/\/rutracker.nl\/forum\/index.php\n< CF-Cache-Status: DYNAMIC\n< Expect-CT: max-age=604800, report-uri="https:\/\/report-uri.cloudflare.com\/cdn-cgi\/beacon\/expect-ct"\n< Server: cloudflare\n< CF-RAY: 52feee696f42d891-CPH\n<\/code><\/pre>\n
\"Domen-frontend<\/p>\n
U ovom slu\u010daju pristupili smo blokiranom serveru rutracker.nl koriste\u0107i DoH resolver dns.google (nema gre\u0161ke, sada slavni korporacija ima svoju domenu prvog nivoa) i prikrili se ve\u0107 drugom domenom, \u010dije blokiranje je strogo zabranjeno svim DPI-jevima pod prijetnjom smrtnog kazne. Po dobijenom odgovoru mo\u017eemo shvatiti da je na\u0161 zahtev uspe\u0161no obra\u0111en.<\/p>\n
Kao dodatna provera da li provajderski DPI reaguje na otvoreni SNI, koji \u0161aljemo kao prikriva\u010d \u2014 mo\u017eemo izvr\u0161iti zahtev ka rutracker.nl prikrivaju\u0107i se nekim drugim zabranjenim resursima, na primer, drugim 'dobrim' torrent trackerima:<\/p>\n
$ ESNI_COVER=\"rutor.info\" DOH_URL=https:\/\/dns.google\/dns-query .\/curl-esni https:\/\/rutracker.nl\/<\/code><\/pre>\n
Odgovor od servera ne\u0107emo dobiti, jer \u0107e na\u0161 zahtev biti blokiran DPI sistemom.<\/p>\n
Malo zaklju\u010dak prve delove<\/h3>\n
Dakle, uspeli smo pokazati funkcionalnost eSNI pomo\u0107u openssl i curl i proveriti rad domen-frontinga zasnovanog na eSNI. Na isti na\u010din mo\u017eemo prilagoditi na\u0161e omiljene alate koji koriste openssl biblioteku za rad 'pod prikriva\u010dem' drugih domena. Vi\u0161e o tome u na\u0161im narednim \u010dlancima.<\/p>\n
Izvor: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0421\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0435 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0435 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0444\u0438\u043b\u044c\u0442\u0440\u0430\u0446\u0438\u0438 \u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430, \u043e\u0442 \u0442\u0430\u043a\u0438\u0445 \u0438\u043c\u0435\u043d\u0438\u0442\u044b\u0445 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u0435\u0439 \u043a\u0430\u043a Cisco, BlueCoat, FireEye \u0438\u043c\u0435\u044e\u0442 \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0449\u0435\u0433\u043e \u0441 \u0431\u043e\u043b\u0435\u0435 \u043c\u043e\u0449\u043d\u044b\u043c\u0438 \u0438\u0445 \u0441\u043e\u0431\u0440\u0430\u0442\u044c\u044f\u043c\u0438 \u2014 DPI \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0443\u0441\u0438\u043b\u0435\u043d\u043d\u043e \u0432\u043d\u0435\u0434\u0440\u044f\u044e\u0442\u0441\u044f \u043d\u0430 \u043d\u0430\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u043c \u0443\u0440\u043e\u0432\u043d\u0435. \u0421\u0443\u0442\u044c \u0440\u0430\u0431\u043e\u0442\u044b \u0438 \u0442\u0435\u0445 \u0438 \u0434\u0440\u0443\u0433\u0438\u0445 \u0432 \u0442\u043e\u043c, \u0447\u0442\u043e\u0431\u044b \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u044c \u0434\u043e\u0441\u043c\u043e\u0442\u0440 \u0432\u0445\u043e\u0434\u044f\u0449\u0435\u0433\u043e \u0438 \u0438\u0441\u0445\u043e\u0434\u044f\u0449\u0435\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430 \u0438, \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0430\u043d\u0438\u0438 \u0447\u0435\u0440\u043d\u044b\u0445\/\u0431\u0435\u043b\u044b\u0445 \u0441\u043f\u0438\u0441\u043a\u043e\u0432, \u043f\u0440\u0438\u043d\u0438\u043c\u0430\u0442\u044c \u0440\u0435\u0448\u0435\u043d\u0438\u0435 […]<\/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":[688],"tags":[],"class_list":["post-52639","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Domen-fronting na bazi TLS 1.3 | ProHoster","description":"Uvod Savremeni korporativni sistemi filtriranja.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/domen-fronting-na-baze-tls-1-3","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\u0414\u043e\u043c\u0435\u043d-\u0444\u0440\u043e\u043d\u0442\u0438\u043d\u0433 \u043d\u0430 \u0431\u0430\u0437\u0435 TLS 1.3 | ProHoster","og:description":"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0421\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0435 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0435 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0444\u0438\u043b\u044c\u0442\u0440\u0430\u0446\u0438\u0438.","og:url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/domen-fronting-na-baze-tls-1-3","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":"2019-11-12T21:00:00+00:00","article:modified_time":"2026-05-20T17:54:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"52639","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":"2026-01-24 04:19:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:39:27","updated":"2026-01-24 04:19:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/52639","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=52639"}],"version-history":[{"count":3,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/52639\/revisions"}],"predecessor-version":[{"id":173323,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/52639\/revisions\/173323"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=52639"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=52639"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=52639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}