{"id":478241,"date":"2023-08-09T09:29:36","date_gmt":"2023-08-09T09:29:36","guid":{"rendered":""},"modified":"2023-09-05T11:16:21","modified_gmt":"2023-09-05T11:16:21","slug":"oauth","status":"publish","type":"wiki","link":"https:\/\/oneproxy.pro\/tr\/wiki\/oauth\/","title":{"rendered":"Yemin"},"content":{"rendered":"<p>&quot;A\u00e7\u0131k Yetkilendirme&quot;nin k\u0131saltmas\u0131 olan OAuth, kimlik bilgilerini (\u00f6r. kullan\u0131c\u0131 ad\u0131 ve \u015fifre) do\u011frudan uygulamalarla payla\u015fmadan, kullan\u0131c\u0131lara \u00fc\u00e7\u00fcnc\u00fc taraf uygulamalara kaynaklar\u0131na s\u0131n\u0131rl\u0131 eri\u015fim vermeleri i\u00e7in g\u00fcvenli ve standartla\u015ft\u0131r\u0131lm\u0131\u015f bir yol sa\u011flayan a\u00e7\u0131k standart bir \u00e7er\u00e7evedir. . Yayg\u0131n olarak benimsenen bu protokol, daha iyi g\u00fcvenlik ve kullan\u0131c\u0131 gizlili\u011fi sa\u011flarken, internetteki \u00e7e\u015fitli hizmetler aras\u0131nda kusursuz entegrasyon sa\u011flar.<\/p>\n<h2>OAuth&#039;un k\u00f6keninin tarihi ve ilk s\u00f6z\u00fc<\/h2>\n<p>OAuth&#039;un k\u00f6kleri, Blaine Cook ve Chris Messina taraf\u0131ndan ilk kez kavramsalla\u015ft\u0131r\u0131ld\u0131\u011f\u0131 2006 y\u0131l\u0131na kadar uzanabilir ve \u00fc\u00e7\u00fcnc\u00fc taraf uygulamalar taraf\u0131ndan Twitter hesaplar\u0131na yetki verilmi\u015f eri\u015fim sa\u011flama ihtiyac\u0131ndan ilham al\u0131narak tasarlanm\u0131\u015ft\u0131r. K\u0131sa bir s\u00fcre sonra 2007 y\u0131l\u0131nda Eran Hammer taraf\u0131ndan OAuth 1.0 tasla\u011f\u0131 tan\u0131t\u0131ld\u0131 ve ilk OAuth protokol\u00fc yay\u0131nland\u0131. Protokol\u00fcn g\u00fcncellenmi\u015f ve daha g\u00fcvenli bir s\u00fcr\u00fcm\u00fc olan OAuth 1.0a, 2009&#039;da sonland\u0131r\u0131ld\u0131. O zamandan bu yana standart geli\u015fti ve 2012&#039;de piyasaya s\u00fcr\u00fclen ve selefinin s\u0131n\u0131rlamalar\u0131n\u0131 ele alan OAuth 2.0&#039;\u0131n ortaya \u00e7\u0131kmas\u0131na yol a\u00e7t\u0131.<\/p>\n<h2>OAuth hakk\u0131nda detayl\u0131 bilgi: OAuth konusunu geni\u015fletme<\/h2>\n<p>OAuth, kullan\u0131c\u0131 verilerinin g\u00fcvenli\u011finin sa\u011flanmas\u0131nda ve farkl\u0131 hizmet ve uygulamalar\u0131n kusursuz entegrasyonunda \u00f6nemli bir rol oynar. OAuth, hassas kimlik bilgilerini payla\u015fmak yerine, \u00fc\u00e7\u00fcnc\u00fc taraf bir uygulaman\u0131n sosyal medya siteleri, bulut depolama hizmetleri ve daha fazlas\u0131 gibi belirli platformlardaki kullan\u0131c\u0131 verilerine eri\u015fmesine olanak tan\u0131yan ge\u00e7ici kimlik bilgileri olan eri\u015fim belirte\u00e7lerini kullan\u0131r. Belirte\u00e7lerin kapsam\u0131 s\u0131n\u0131rl\u0131d\u0131r ve bir son kullanma s\u00fcresi vard\u0131r, bu da onlar\u0131 do\u011frudan parola payla\u015fmaktan daha g\u00fcvenli k\u0131lar.<\/p>\n<h2>OAuth&#039;un i\u00e7 yap\u0131s\u0131: OAuth nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n<p>OAuth birden fazla varl\u0131\u011f\u0131 i\u00e7erir: kaynak sahibi (kullan\u0131c\u0131), istemci (\u00fc\u00e7\u00fcnc\u00fc taraf uygulamas\u0131), yetkilendirme sunucusu ve kaynak sunucusu. OAuth ak\u0131\u015f\u0131 genellikle a\u015fa\u011f\u0131daki ad\u0131mlardan olu\u015fur:<\/p>\n<ol>\n<li>\n<p><strong>Kullan\u0131c\u0131 Yetkilendirmesi:<\/strong> Kullan\u0131c\u0131, istemciyi yetkilendirme sunucusuna y\u00f6nlendirerek kaynaklar\u0131na eri\u015fmesine izin verir.<\/p>\n<\/li>\n<li>\n<p><strong>M\u00fc\u015fteri Kayd\u0131:<\/strong> \u0130stemci, yetkilendirme sunucusuna kay\u0131tl\u0131d\u0131r ve kimlik do\u011frulama i\u00e7in kullan\u0131lan istemci kimlik bilgilerini (\u00f6rne\u011fin, istemci kimli\u011fi ve istemci s\u0131rr\u0131) al\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>Yetki Verilmesi:<\/strong> Kullan\u0131c\u0131 izin verdikten sonra yetkilendirme sunucusu, istemciye bir yetkilendirme izni (\u00f6rne\u011fin, bir yetkilendirme kodu veya eri\u015fim belirteci) verir.<\/p>\n<\/li>\n<li>\n<p><strong>Eri\u015fim Jetonu \u0130ste\u011fi:<\/strong> Daha sonra istemci, elde edilen yetkilendirme iznini kullanarak yetkilendirme sunucusundan bir eri\u015fim belirteci ister.<\/p>\n<\/li>\n<li>\n<p><strong>Kaynaklara Eri\u015fim:<\/strong> \u0130stemci, kullan\u0131c\u0131n\u0131n korunan kaynaklar\u0131na eri\u015fmek i\u00e7in eri\u015fim belirtecini kaynak sunucusuna sunar.<\/p>\n<\/li>\n<li>\n<p><strong>Kaynak Eri\u015fimi:<\/strong> Eri\u015fim belirteci ge\u00e7erli ve yetkiliyse kaynak sunucusu, istemcinin istenen kaynaklara eri\u015fmesine izin verir.<\/p>\n<\/li>\n<\/ol>\n<h2>OAuth&#039;un temel \u00f6zelliklerinin analizi<\/h2>\n<p>OAuth, onu sa\u011flam ve yayg\u0131n olarak benimsenen bir yetkilendirme \u00e7er\u00e7evesi haline getiren \u00e7e\u015fitli temel \u00f6zelliklere sahiptir:<\/p>\n<ol>\n<li>\n<p><strong>G\u00fcvenlik:<\/strong> OAuth&#039;un tasar\u0131m\u0131, kullan\u0131c\u0131 kimlik bilgilerini gizli tutarak ve yaln\u0131zca eri\u015fim belirte\u00e7leri arac\u0131l\u0131\u011f\u0131yla eri\u015fime izin vererek g\u00fcvenli\u011fini sa\u011flar.<\/p>\n<\/li>\n<li>\n<p><strong>Kullan\u0131c\u0131 Onay\u0131:<\/strong> OAuth, kaynaklara eri\u015fim izni vermeden \u00f6nce kullan\u0131c\u0131n\u0131n a\u00e7\u0131k iznini gerektirir ve kullan\u0131c\u0131lara verilerinin kontrol\u00fcn\u00fc verir.<\/p>\n<\/li>\n<li>\n<p><strong>S\u0131n\u0131rl\u0131 eri\u015fim:<\/strong> Eri\u015fim belirte\u00e7lerinin s\u0131n\u0131rl\u0131 bir kapsam\u0131 ve ge\u00e7erlili\u011fi vard\u0131r, bu da hassas bilgilere yetkisiz eri\u015fim riskini azalt\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>\u00dc\u00e7\u00fcnc\u00fc Taraf Entegrasyonu:<\/strong> OAuth, hassas verileri a\u00e7\u0131\u011fa \u00e7\u0131karmadan farkl\u0131 platformlar ve hizmetler aras\u0131nda kusursuz entegrasyonu kolayla\u015ft\u0131r\u0131r.<\/p>\n<\/li>\n<\/ol>\n<h2>OAuth T\u00fcrleri: Tablolar\u0131 ve listeleri kullanma<\/h2>\n<p>OAuth&#039;un her biri farkl\u0131 kullan\u0131m senaryolar\u0131na ve senaryolara hitap eden birden fazla izin t\u00fcr\u00fc vard\u0131r. En s\u0131k kullan\u0131lan hibe t\u00fcrleri \u015funlard\u0131r:<\/p>\n<table>\n<thead>\n<tr>\n<th>Hibe T\u00fcr\u00fc<\/th>\n<th>Tan\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Yetki Kodu<\/td>\n<td>Web uygulamalar\u0131 i\u00e7in kullan\u0131l\u0131r ve bir eri\u015fim belirteciyle yetkilendirme kodunun de\u011fi\u015fimini i\u00e7eren iki ad\u0131ml\u0131 bir s\u00fcreci izler.<\/td>\n<\/tr>\n<tr>\n<td>\u00d6rt\u00fcl\u00fc<\/td>\n<td>Eri\u015fim belirtecinin do\u011frudan istemciye d\u00f6nd\u00fcr\u00fcld\u00fc\u011f\u00fc mobil ve istemci taraf\u0131 uygulamalar i\u00e7in optimize edilmi\u015ftir.<\/td>\n<\/tr>\n<tr>\n<td>Kaynak Sahibi Parolas\u0131 Kimlik Bilgileri<\/td>\n<td>Kullan\u0131c\u0131lar\u0131n kimlik bilgilerini do\u011frudan bir eri\u015fim belirteci kar\u015f\u0131l\u0131\u011f\u0131nda de\u011fi\u015ftirmelerine olanak tan\u0131r. Kamu istemcileri i\u00e7in \u00f6nerilmez.<\/td>\n<\/tr>\n<tr>\n<td>M\u00fc\u015fteri Kimlik Bilgileri<\/td>\n<td>\u0130stemcinin kaynak sahibi ad\u0131na hareket etti\u011fi makineler aras\u0131 ileti\u015fim i\u00e7in uygundur.<\/td>\n<\/tr>\n<tr>\n<td>Jetonu Yenile<\/td>\n<td>\u0130stemcilerin yeniden yetkilendirmeye gerek kalmadan yeni bir eri\u015fim belirteci istemesine olanak tan\u0131yarak g\u00fcvenli\u011fi ve kullan\u0131labilirli\u011fi art\u0131r\u0131r.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>OAuth&#039;u kullanma yollar\u0131, kullan\u0131mla ilgili sorunlar ve \u00e7\u00f6z\u00fcmleri<\/h2>\n<p>OAuth, a\u015fa\u011f\u0131dakiler de dahil olmak \u00fczere \u00e7e\u015fitli uygulama ve hizmetlerde yayg\u0131n olarak kullan\u0131l\u0131r:<\/p>\n<ol>\n<li>\n<p><strong>Sosyal Medya Entegrasyonu:<\/strong> OAuth, kullan\u0131c\u0131lar\u0131n sosyal medya hesaplar\u0131n\u0131 kullanarak \u00fc\u00e7\u00fcnc\u00fc taraf uygulamalara g\u00fcvenli bir \u015fekilde giri\u015f yapmalar\u0131n\u0131 sa\u011flar.<\/p>\n<\/li>\n<li>\n<p><strong>Bulut Depolama Hizmetleri:<\/strong> Uygulamalar\u0131n Dropbox ve Google Drive gibi bulut platformlar\u0131nda depolanan dosyalara eri\u015fmesine ve bunlar\u0131 y\u00f6netmesine olanak tan\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>Tek Oturum A\u00e7ma (SSO):<\/strong> OAuth, SSO&#039;yu etkinle\u015ftirmek ve birden fazla platformda oturum a\u00e7ma s\u00fcrecini kolayla\u015ft\u0131rmak i\u00e7in kullan\u0131l\u0131r.<\/p>\n<\/li>\n<\/ol>\n<p>G\u00fc\u00e7l\u00fc y\u00f6nlerine ra\u011fmen OAuth uygulamalar\u0131 a\u015fa\u011f\u0131daki gibi zorluklarla kar\u015f\u0131la\u015fabilir:<\/p>\n<ul>\n<li>\n<p><strong>G\u00fcvenlik endi\u015feleri:<\/strong> K\u00f6t\u00fc uygulanan OAuth, g\u00fcvenlik a\u00e7\u0131klar\u0131na ve veri ihlallerine yol a\u00e7abilir.<\/p>\n<\/li>\n<li>\n<p><strong>Jeton Y\u00f6netimi:<\/strong> Eri\u015fim belirte\u00e7lerinin i\u015flenmesi ve g\u00fcvenli\u011finin sa\u011flanmas\u0131, \u00f6zellikle b\u00fcy\u00fck \u00f6l\u00e7ekli uygulamalarda karma\u015f\u0131k olabilir.<\/p>\n<\/li>\n<li>\n<p><strong>Kullan\u0131c\u0131 deneyimi:<\/strong> OAuth&#039;un izin s\u00fcreci baz\u0131 kullan\u0131c\u0131lar i\u00e7in kafa kar\u0131\u015ft\u0131r\u0131c\u0131 olabilir ve genel kullan\u0131c\u0131 deneyimini etkileyebilir.<\/p>\n<\/li>\n<\/ul>\n<p>Bu zorluklar\u0131n \u00e7\u00f6z\u00fcmleri aras\u0131nda d\u00fczenli g\u00fcvenlik denetimleri, belirte\u00e7 \u015fifreleme ve kullan\u0131c\u0131 onay\u0131 aray\u00fczlerinin iyile\u015ftirilmesi yer al\u0131yor.<\/p>\n<h2>Ana \u00f6zellikler ve benzer terimlerle di\u011fer kar\u015f\u0131la\u015ft\u0131rmalar: Tablo ve liste \u015feklinde<\/h2>\n<table>\n<thead>\n<tr>\n<th>OAuth ve OAuth 2.0 kar\u015f\u0131la\u015ft\u0131rmas\u0131<\/th>\n<th>OAuth<\/th>\n<th>OAuth 2.0<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>S\u00fcr\u00fcm<\/td>\n<td>OAuth 1.0<\/td>\n<td>OAuth 2.0<\/td>\n<\/tr>\n<tr>\n<td>Basitlik<\/td>\n<td>Daha karma\u015f\u0131k<\/td>\n<td>Daha basit ve daha ak\u0131c\u0131<\/td>\n<\/tr>\n<tr>\n<td>G\u00fcvenlik<\/td>\n<td>Daha az g\u00fcvenli<\/td>\n<td>Do\u011fru uygulamalarla geli\u015ftirilmi\u015f g\u00fcvenlik<\/td>\n<\/tr>\n<tr>\n<td>Benimseme<\/td>\n<td>S\u0131n\u0131rl\u0131<\/td>\n<td>B\u00fcy\u00fck \u015firketler ve hizmetler taraf\u0131ndan yayg\u0131n olarak benimsenmi\u015ftir<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>OAuth ile ilgili gelece\u011fin perspektifleri ve teknolojileri<\/h2>\n<p>OAuth&#039;un gelece\u011fi muhtemelen g\u00fcvenlik \u00f6nlemlerini geli\u015ftirmeye ve kullan\u0131c\u0131 deneyimini iyile\u015ftirmeye odaklanacak. Ortaya \u00e7\u0131kan baz\u0131 teknolojiler ve trendler \u015funlar\u0131 i\u00e7erir:<\/p>\n<ol>\n<li>\n<p><strong>OAuth 2.1:<\/strong> G\u00fcvenlik endi\u015felerini gidermeye ve standard\u0131 daha da geli\u015ftirmeye y\u00f6nelik potansiyel bir g\u00fcncelleme.<\/p>\n<\/li>\n<li>\n<p><strong>Jetonsuz Kimlik Do\u011frulama:<\/strong> Geleneksel eri\u015fim belirte\u00e7leri gerektirmeyen alternatif kimlik do\u011frulama y\u00f6ntemlerini ke\u015ffetme.<\/p>\n<\/li>\n<li>\n<p><strong>Merkezi Olmayan Kimlik:<\/strong> Daha fazla gizlilik ve kullan\u0131c\u0131 kontrol\u00fc i\u00e7in OAuth&#039;un merkezi olmayan kimlik sistemleriyle entegre edilmesi.<\/p>\n<\/li>\n<\/ol>\n<h2>Proxy sunucular\u0131 nas\u0131l kullan\u0131labilir veya OAuth ile nas\u0131l ili\u015fkilendirilebilir?<\/h2>\n<p>Proxy sunucular\u0131, OAuth uygulamalar\u0131n\u0131n g\u00fcvenli\u011fini ve performans\u0131n\u0131 art\u0131rmada \u00e7ok \u00f6nemli bir rol oynar. \u0130stemci ile yetkilendirme sunucusu aras\u0131nda arac\u0131 g\u00f6revi g\u00f6rerek Da\u011f\u0131t\u0131lm\u0131\u015f Hizmet Reddi (DDoS) sald\u0131r\u0131lar\u0131 gibi potansiyel sald\u0131r\u0131lara kar\u015f\u0131 ek bir koruma katman\u0131 sa\u011flarlar. \u0130steklerin proxy sunucular \u00fczerinden y\u00f6nlendirilmesi, sald\u0131rganlar\u0131n do\u011frudan yetkilendirme sunucusunu hedeflemesini zorla\u015ft\u0131rarak genel g\u00fcvenlik durumunu art\u0131r\u0131r.<\/p>\n<p>Ayr\u0131ca proxy sunucular, s\u0131k talep edilen kaynaklar\u0131 \u00f6nbelle\u011fe alarak, yetkilendirme sunucusu \u00fczerindeki y\u00fck\u00fc azaltarak ve istemcilerin yan\u0131t s\u00fcrelerini optimize ederek performans\u0131 art\u0131rabilir.<\/p>\n<h2>\u0130lgili Ba\u011flant\u0131lar<\/h2>\n<p>OAuth hakk\u0131nda daha fazla bilgi i\u00e7in a\u015fa\u011f\u0131daki kaynaklara ba\u015fvurabilirsiniz:<\/p>\n<ol>\n<li><a href=\"https:\/\/oauth.net\/2\/\" target=\"_new\" rel=\"noopener nofollow\">OAuth 2.0 Spesifikasyonu<\/a><\/li>\n<li><a href=\"https:\/\/tools.ietf.org\/html\/rfc6749\" target=\"_new\" rel=\"noopener nofollow\">OAuth 2.0 RFC<\/a><\/li>\n<li><a href=\"https:\/\/oauth.net\/resources\/\" target=\"_new\" rel=\"noopener nofollow\">OAuth Topluluk Kaynaklar\u0131<\/a><\/li>\n<\/ol>\n<p>Sonu\u00e7 olarak OAuth, internette g\u00fcvenli ve kusursuz yetkilendirme i\u00e7in ba\u015fvurulacak standart haline geldi. \u00dc\u00e7\u00fcnc\u00fc taraf eri\u015fimine izin vermek i\u00e7in yap\u0131land\u0131r\u0131lm\u0131\u015f ve standartla\u015ft\u0131r\u0131lm\u0131\u015f bir yakla\u015f\u0131m sunarak, farkl\u0131 platformlar aras\u0131nda g\u00fc\u00e7l\u00fc entegrasyonlara olanak tan\u0131rken kullan\u0131c\u0131lara g\u00fc\u00e7 verir. Teknoloji geli\u015fmeye devam ettik\u00e7e OAuth da \u015f\u00fcphesiz onunla birlikte geli\u015fecek ve g\u00fcvenli veri payla\u015f\u0131m\u0131 ve kullan\u0131c\u0131 gizlili\u011finin temel dayana\u011f\u0131 olma konumunu koruyacakt\u0131r.<\/p>","protected":false},"featured_media":478242,"menu_order":0,"template":"","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"class_list":["post-478241","wiki","type-wiki","status-publish","has-post-thumbnail","hentry"],"acf":{"faq_title":"Frequently Asked Questions about <mark>OAuth: Empowering Secure and Convenient Authorization<\/mark>","faq_items":[{"question":"What is OAuth?","answer":"<p>OAuth, short for \"Open Authorization,\" is an open standard framework that provides a secure and standardized way for users to grant third-party applications limited access to their resources without sharing their credentials directly. It ensures better security and user privacy while enabling seamless integration between various services on the internet.<\/p>"},{"question":"How did OAuth originate, and when was it first introduced?","answer":"<p>OAuth's origins can be traced back to 2006 when it was conceptualized by Blaine Cook and Chris Messina to enable delegated access to Twitter accounts. The first OAuth protocol draft was introduced by Eran Hammer in 2007. OAuth 1.0a, an updated and more secure version, was finalized in 2009. OAuth 2.0, addressing limitations, was released in 2012.<\/p>"},{"question":"How does OAuth work?","answer":"<p>OAuth involves multiple entities: the resource owner (user), the client (third-party application), the authorization server, and the resource server. The process includes user authorization, client registration, obtaining an authorization grant, requesting an access token, accessing resources, and granting access based on the token's validity.<\/p>"},{"question":"What are the key features of OAuth?","answer":"<p>OAuth's key features include enhanced security by avoiding direct credential sharing, user consent for resource access, limited access through access tokens, and seamless integration between platforms.<\/p>"},{"question":"What are the types of OAuth?","answer":"<p>OAuth offers various grant types tailored for specific use cases:<\/p><ol><li>Authorization Code: For web applications, exchanging an authorization code for an access token.<\/li><li>Implicit: For mobile and client-side apps, direct access token return to the client.<\/li><li>Resource Owner Password Credentials: Direct exchange of credentials for an access token.<\/li><li>Client Credentials: For machine-to-machine communication where the client acts on behalf of the resource owner.<\/li><li>Refresh Token: Enables obtaining a new access token without reauthorization.<\/li><\/ol>"},{"question":"How is OAuth used, and what challenges might arise?","answer":"<p>OAuth is widely used for social media integration, cloud storage access, and single sign-on (SSO). Challenges may include security concerns, token management complexities, and user experience issues. Solutions involve improved implementations, token encryption, and better user consent interfaces.<\/p>"},{"question":"How does OAuth compare to OAuth 2.0?","answer":"<p>OAuth 1.0 is more complex and less secure compared to OAuth 2.0, which offers a streamlined and improved security-focused approach. OAuth 2.0 is widely adopted by major companies and services.<\/p>"},{"question":"What are the future perspectives for OAuth?","answer":"<p>The future of OAuth will likely focus on enhancing security and user experience. Potential developments include OAuth 2.1 updates, exploring tokenless authentication, and integrating with decentralized identity systems.<\/p>"},{"question":"How do proxy servers relate to OAuth?","answer":"<p>Proxy servers enhance OAuth security and performance by acting as intermediaries between the client and the authorization server. They provide an additional layer of protection against attacks and improve response times by caching frequently requested resources.<\/p>"}]},"_links":{"self":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/478241","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki"}],"about":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/types\/wiki"}],"version-history":[{"count":0,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/478241\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media\/478242"}],"wp:attachment":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media?parent=478241"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}