{"id":1999,"date":"2026-04-13T10:05:33","date_gmt":"2026-04-13T07:05:33","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1999"},"modified":"2026-08-02T12:09:02","modified_gmt":"2026-08-02T12:09:02","slug":"wordpress-formlari-ve-ajax-istekleri-mixed-content-nedeniyle-engelleniyor","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-formlari-ve-ajax-istekleri-mixed-content-nedeniyle-engelleniyor\/","title":{"rendered":"WordPress Formlar\u0131 ve AJAX \u0130stekleri Mixed Content Nedeniyle Engelleniyorsa"},"content":{"rendered":"

HTTPS sayfa d\u00fczg\u00fcn g\u00f6r\u00fcnse de form g\u00f6nderildi\u011finde taray\u0131c\u0131 HTTP admin-ajax.php<\/code> veya REST endpoint’ini engelleyebilir. \u0130stek WordPress’e hi\u00e7 ula\u015fmad\u0131\u011f\u0131 i\u00e7in sunucu g\u00fcnl\u00fc\u011f\u00fcnde kay\u0131t bulunmayabilir.<\/p>\n

Network panelinde Preserve log’u a\u00e7\u0131p g\u00fcvenli test verisi g\u00f6nderin. \u0130stek URL’si, initiator, y\u00f6ntem ve konsol mesaj\u0131 sorunun mixed content mi, CORS mu yoksa nonce hatas\u0131 m\u0131 oldu\u011funu ay\u0131r\u0131r.<\/p>\n

\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. Form mixed content nedir?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i \u00f6rnek<\/a><\/li>\n
  3. Neden \u00f6nemlidir?<\/a><\/li>\n
  4. \u00c7\u00f6z\u00fcm ad\u0131mlar\u0131<\/a><\/li>\n
  5. \u0130leri kontroller<\/a><\/li>\n
  6. Riskler<\/a><\/li>\n
  7. AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/a><\/li>\n
  8. \u0130lgili yaz\u0131lar<\/a><\/li>\n
  9. Sonu\u00e7<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    Form mixed content nedir?<\/h2>\n

    HTTPS belgedeki form action, fetch, XHR, REST veya admin-ajax.php<\/code> \u00e7a\u011fr\u0131s\u0131 HTTP hedefe gidiyorsa taray\u0131c\u0131 iste\u011fi engeller. URL; WordPress adresinden, JavaScript’e aktar\u0131lan veriden, eklenti ayar\u0131ndan veya proxy’nin HTTPS bilgisini yanl\u0131\u015f iletmesinden \u00fcretilebilir.<\/p>\n

    Ger\u00e7ek\u00e7i \u00f6rnek<\/h2>\n

    Ta\u015f\u0131ma sonras\u0131nda ileti\u015fim formunun JavaScript ayar\u0131nda eski HTTP AJAX adresi kal\u0131r. Sayfa cache’i de eski nonce ve endpoint’i sunar. Taray\u0131c\u0131 iste\u011fi g\u00f6ndermedi\u011finden form eklentisi veya posta sistemi hen\u00fcz devreye girmemi\u015ftir.<\/p>\n

    Neden \u00f6nemlidir?<\/h2>\n

    Form, \u00f6deme ve hesap i\u015flemleri sessizce ba\u015far\u0131s\u0131z olabilir. Sorunu \u00e7\u00f6zmek i\u00e7in CORS, nonce veya taray\u0131c\u0131 g\u00fcvenli\u011fini kapatmak korumay\u0131 kald\u0131r\u0131r; do\u011fru endpoint’i \u00fcretmez.<\/p>\n

    \u00c7\u00f6z\u00fcm ad\u0131mlar\u0131<\/h2>\n
      \n
    1. Anonim oturumda zarars\u0131z bir test g\u00f6nderimi yap\u0131n.<\/li>\n
    2. HTTP endpoint’ini ve onu \u00fcreten script\/ayar\u0131 bulun.<\/li>\n
    3. Reverse proxy kullan\u0131l\u0131yorsa WordPress adreslerini d\u00fczeltin ve proxy’nin istemcinin HTTPS kulland\u0131\u011f\u0131n\u0131 do\u011fru iletti\u011fini do\u011frulay\u0131n.<\/li>\n
    4. Eklenti veya yerelle\u015ftirilmi\u015f betik verisini HTTPS endpoint’ine g\u00fcncelleyin.<\/li>\n
    5. \u0130lgili sayfa cache’ini yenileyip g\u00fcncel nonce ve URL’yi do\u011frulay\u0131n.<\/li>\n
    6. \u0130ste\u011fin tek kez g\u00f6nderildi\u011fini, sunucuya ula\u015ft\u0131\u011f\u0131n\u0131 ve do\u011fru yan\u0131t d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc s\u0131nay\u0131n.<\/li>\n<\/ol>\n

      \u0130leri kontroller<\/h2>\n

      Form action, fetch\/XHR URL’si, nonce, \u00e7erez kapsam\u0131, CORS ve CSP mesaj\u0131n\u0131 birlikte inceleyin. Captcha, \u00f6deme SDK’s\u0131, CRM veya dosya y\u00fckleme hedefi gibi taray\u0131c\u0131 ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131n da HTTPS kulland\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n. Sunucudan sunucuya webhook’u taray\u0131c\u0131 iste\u011fiyle kar\u0131\u015ft\u0131rmay\u0131n.<\/p>\n

      Riskler<\/h2>\n

      Canl\u0131 g\u00f6nderimi tekrar tekrar denemek sipari\u015f, e-posta veya m\u00fc\u015fteri kayd\u0131n\u0131 \u00e7o\u011faltabilir. Test verisi ve idempotency korumas\u0131 kullan\u0131n. JavaScript optimizasyonunu b\u00fct\u00fcn\u00fcyle kapatmak yerine yaln\u0131z ilgili dosyada kar\u015f\u0131la\u015ft\u0131rma yap\u0131n.<\/p>\n

      \n

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

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

      Form veya AJAX endpoint’i HTTPS’ye ge\u00e7irildikten sonra AIOWS SSL Y\u00f6neticisi, WordPress adresleriyle uygulaman\u0131n g\u00fcvenli ba\u011flant\u0131 durumunu denetlemeye yard\u0131mc\u0131 olur.<\/p>\n

      Mod\u00fcl form eklentisinin endpoint mant\u0131\u011f\u0131n\u0131, CORS politikas\u0131n\u0131 veya d\u0131\u015f \u00f6deme hizmetini otomatik onarmaz. Taray\u0131c\u0131daki ger\u00e7ek iste\u011fi izleyip URL’yi \u00fcreten katmanda d\u00fczeltme yap\u0131n.<\/p>\n

      HTTPS iste\u011fi sunucuya ula\u015ft\u0131ktan sonra 403 ya da nonce hatas\u0131 al\u0131yorsan\u0131z mixed content \u00e7\u00f6z\u00fclm\u00fc\u015ft\u00fcr; yeni sorunu kendi g\u00fcvenlik ba\u011flam\u0131nda inceleyin ve korumalar\u0131 kapatmay\u0131n.<\/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 yaz\u0131lar<\/h2>\n