{"id":1978,"date":"2026-08-20T13:36:34","date_gmt":"2026-08-20T10:36:34","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1978"},"modified":"2026-08-04T11:29:01","modified_gmt":"2026-08-04T11:29:01","slug":"reverse-proxy-arkasinda-wordpress-https-sorunlari","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/reverse-proxy-arkasinda-wordpress-https-sorunlari\/","title":{"rendered":"Reverse Proxy Arkas\u0131nda WordPress HTTPS Sorunlar\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?"},"content":{"rendered":"

Reverse proxy TLS ba\u011flant\u0131s\u0131n\u0131 sonland\u0131r\u0131p WordPress’e HTTP ile ba\u011fland\u0131\u011f\u0131nda ziyaret\u00e7i HTTPS kullanmas\u0131na ra\u011fmen uygulama iste\u011fi g\u00fcvensiz sanabilir. Bunun sonucunda y\u00f6nlendirme d\u00f6ng\u00fcs\u00fc, HTTP canonical URL’ler, Secure olmayan \u00e7erezler veya hatal\u0131 callback adresleri olu\u015fabilir.<\/p>\n

\u0130stemcinin kulland\u0131\u011f\u0131 protokol\u00fc ve HTTPS durumunu WordPress’e do\u011fru iletmek gerekir; ancak istemcinin g\u00f6nderdi\u011fi her forwarded ba\u015fl\u0131\u011f\u0131na g\u00fcvenilmemelidir. G\u00fcven yaln\u0131z bilinen proxy s\u0131n\u0131r\u0131nda kurulmal\u0131d\u0131r.<\/p>\n

\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. Proxy arkas\u0131nda HTTPS nas\u0131l i\u015fler?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/a><\/li>\n
  3. Neden \u00f6nemlidir?<\/a><\/li>\n
  4. Temel \u00e7\u00f6z\u00fcm ad\u0131mlar\u0131<\/a><\/li>\n
  5. \u0130leri teknik kontroller<\/a><\/li>\n
  6. Riskler ve geri alma<\/a><\/li>\n
  7. AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/a><\/li>\n
  8. \u0130lgili AIOWS yaz\u0131lar\u0131<\/a><\/li>\n
  9. Sonu\u00e7 ve \u00f6nerilen yol<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    Proxy arkas\u0131nda HTTPS nas\u0131l i\u015fler?<\/h2>\n

    Ziyaret\u00e7i ile proxy aras\u0131ndaki ve proxy ile origin aras\u0131ndaki ba\u011flant\u0131lar ayr\u0131 olabilir. WordPress, istemcinin kulland\u0131\u011f\u0131 protokol\u00fc ve istedi\u011fi hostu proxy’nin g\u00fcvenilir bi\u00e7imde d\u00fczenledi\u011fi ba\u015fl\u0131klardan \u00f6\u011frenmelidir. Aksi h\u00e2lde URL, \u00e7erez ve y\u00f6nlendirme \u00fcretimi i\u00e7 ba\u011flant\u0131ya g\u00f6re yap\u0131l\u0131r.<\/p>\n

    Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/h2>\n

    Load balancer HTTPS iste\u011fini kabul eder, origin’e HTTP g\u00f6nderir ve X-Forwarded-Proto: https<\/code> ekler. WordPress bu bilgiyi kullanmad\u0131\u011f\u0131 i\u00e7in wp-admin<\/code> iste\u011fini yeniden HTTPS’ye y\u00f6nlendirir. Ayn\u0131 proxy iste\u011fi yine HTTP ile origin’e iletti\u011finden d\u00f6ng\u00fc olu\u015fur.<\/p>\n

    Ba\u015fka bir yap\u0131land\u0131rmada proxy istemcinin mevcut ba\u015fl\u0131\u011f\u0131n\u0131 ezmek yerine sonuna ekler. WordPress belirsiz de\u011feri yanl\u0131\u015f yorumlayabilir veya sald\u0131rgan sahte HTTPS bilgisi g\u00f6nderebilir.<\/p>\n

    Neden \u00f6nemlidir?<\/h2>\n

    WordPress \u00f6zg\u00fcn iste\u011fin HTTP mi HTTPS mi kulland\u0131\u011f\u0131n\u0131 yanl\u0131\u015f belirledi\u011finde giri\u015f oturumlar\u0131, REST kimlik do\u011frulamas\u0131, cron \u00e7a\u011fr\u0131lar\u0131, OAuth ve \u00f6deme webhook’lar\u0131 etkilenir. Yaln\u0131z ana sayfan\u0131n a\u00e7\u0131lmas\u0131 b\u00fct\u00fcn uygulama yollar\u0131n\u0131n do\u011fru oldu\u011fu anlam\u0131na gelmez.<\/p>\n

    Temel \u00e7\u00f6z\u00fcm ad\u0131mlar\u0131<\/h2>\n
      \n
    1. CDN, load balancer, ingress ve origin dahil proxy zincirini \u00e7\u0131kar\u0131n.<\/li>\n
    2. TLS’nin hangi katmanda sonland\u0131\u011f\u0131n\u0131 ve proxy’nin origin’e hangi protokolle ba\u011fland\u0131\u011f\u0131n\u0131 kaydedin.<\/li>\n
    3. Proxy’nin istemcinin kulland\u0131\u011f\u0131 protokol ve host bilgisini g\u00fcvenilir ba\u015fl\u0131klarla iletmesini sa\u011flay\u0131n.<\/li>\n
    4. WordPress ba\u015flamadan \u00f6nce yaln\u0131z bilinen proxy’den gelen HTTPS bilgisini normalle\u015ftirin.<\/li>\n
    5. Y\u00f6nlendirmeyi tek katmanda y\u00f6netin ve do\u011frudan origin eri\u015fimini k\u0131s\u0131tlay\u0131n.<\/li>\n
    6. Giri\u015f, REST, form, callback ve Secure \u00e7erezleri ger\u00e7ek isteklerle s\u0131nay\u0131n.<\/li>\n<\/ol>\n

      \u0130leri teknik kontroller<\/h2>\n

      Ge\u00e7erli, eksik ve sahte forwarded ba\u015fl\u0131klarla edge ve yetkili origin davran\u0131\u015f\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n. Forwarded<\/code>, X-Forwarded-Proto<\/code>, host ve istemci IP zincirinin hangi proxy taraf\u0131ndan yaz\u0131ld\u0131\u011f\u0131n\u0131 belgeleyin. Birden fazla proxy varsa g\u00fcvenilir hop say\u0131s\u0131n\u0131 ve adres aral\u0131\u011f\u0131n\u0131 a\u00e7\u0131k\u00e7a belirleyin.<\/p>\n

      Canonical, site haritas\u0131, REST URL’leri, parola s\u0131f\u0131rlama ve OAuth callback \u00e7\u0131kt\u0131lar\u0131n\u0131 kontrol edin. Proxy sa\u011fl\u0131k denetiminin kullan\u0131c\u0131 trafi\u011finden farkl\u0131 bir host veya protokolle y\u00f6nlendirme olu\u015fturmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n

      Riskler ve geri alma<\/h2>\n

      Her X-Forwarded-Proto<\/code> de\u011ferine g\u00fcvenmek istemcinin g\u00fcvenlik durumunu taklit etmesine izin verir. Yaln\u0131z WordPress URL’lerini de\u011fi\u015ftirmek \u00e7al\u0131\u015fma zaman\u0131ndaki alg\u0131y\u0131 d\u00fczeltmez; her katmana y\u00f6nlendirme eklemek de d\u00f6ng\u00fc olu\u015fturur. De\u011fi\u015fiklikten \u00f6nce proxy ve WordPress yap\u0131land\u0131rmas\u0131n\u0131 kaydedin; giri\u015f veya callback bozulursa son g\u00fcvenilir ba\u015fl\u0131k politikas\u0131na d\u00f6n\u00fcn.<\/p>\n

      \n

      AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/p>\n

      AIOWS SSL Y\u00f6neticisi<\/h2>\n

      Reverse proxy g\u00fcven ili\u015fkisi yap\u0131land\u0131r\u0131ld\u0131ktan sonra AIOWS SSL Y\u00f6neticisi, WordPress’in d\u0131\u015f iste\u011fi HTTPS olarak alg\u0131lad\u0131\u011f\u0131n\u0131 ve do\u011fru adresleri \u00fcretti\u011fini denetlemeye yard\u0131mc\u0131 olur.<\/p>\n

      Mod\u00fcl load balancer veya CDN’nin g\u00fcven politikas\u0131n\u0131 kendi ba\u015f\u0131na de\u011fi\u015ftirmez. Forwarded ba\u015fl\u0131klar\u0131n kayna\u011f\u0131, origin eri\u015fimi ve TLS sonland\u0131rma modeli altyap\u0131 taraf\u0131nda do\u011fru kurulmal\u0131d\u0131r. Sonras\u0131nda WordPress giri\u015fini, REST API’yi, formlar\u0131 ve callback yollar\u0131n\u0131 s\u0131nay\u0131n.<\/p>\n

      Ba\u015fl\u0131k sahtecili\u011fi, y\u00f6nlendirme d\u00f6ng\u00fcs\u00fc veya Secure \u00e7erez sorunu s\u00fcr\u00fcyorsa yeni HTTPS ayarlar\u0131 eklemeyin. Proxy zincirini ve g\u00fcvenilen adresleri yeniden inceleyip son \u00e7al\u0131\u015fan yap\u0131land\u0131rmay\u0131 koruyun.<\/p>\n

      AIOWS SSL Y\u00f6neticisi’ni inceleyin<\/a>AIOWS planlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/p>\n<\/section>\n

      \u0130lgili AIOWS yaz\u0131lar\u0131<\/h2>\n