{"id":1462,"date":"2025-11-06T23:50:38","date_gmt":"2025-11-06T20:50:38","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/nginx-ve-cloudflareda-http-2-ve-http-3-quic-nasil-etkinlestirilir-wordpress-icin-uctan-uca-kurulum-ve-test-rehberi\/"},"modified":"2025-11-06T23:50:38","modified_gmt":"2025-11-06T20:50:38","slug":"nginx-ve-cloudflareda-http-2-ve-http-3-quic-nasil-etkinlestirilir-wordpress-icin-uctan-uca-kurulum-ve-test-rehberi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/nginx-ve-cloudflareda-http-2-ve-http-3-quic-nasil-etkinlestirilir-wordpress-icin-uctan-uca-kurulum-ve-test-rehberi\/","title":{"rendered":"Nginx ve Cloudflare\u2019da HTTP\/2 ve HTTP\/3 (QUIC) Nas\u0131l Etkinle\u015ftirilir? WordPress \u0130\u00e7in U\u00e7tan Uca Kurulum ve Test Rehberi"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Kahven_sogumadan_HTTP2_ve_HTTP3e_beraber_bir_yolculuk\"><span class=\"toc_number toc_depth_1\">1<\/span> Kahven so\u011fumadan: HTTP\/2 ve HTTP\/3\u2019e beraber bir yolculuk<\/a><\/li><li><a href=\"#HTTP2_ve_HTTP3u_anlamak_Aradaki_farki_hissetmek\"><span class=\"toc_number toc_depth_1\">2<\/span> HTTP\/2 ve HTTP\/3\u2019\u00fc anlamak: Aradaki fark\u0131 hissetmek<\/a><\/li><li><a href=\"#Hazirlik_WordPress_Nginx_ve_Cloudflarei_ayni_masaya_oturtmak\"><span class=\"toc_number toc_depth_1\">3<\/span> Haz\u0131rl\u0131k: WordPress, Nginx ve Cloudflare\u2019i ayn\u0131 masaya oturtmak<\/a><\/li><li><a href=\"#Nginx_tarafi_HTTP2yi_saglam_ac_HTTP3u_istege_bagli_dene\"><span class=\"toc_number toc_depth_1\">4<\/span> Nginx taraf\u0131: HTTP\/2\u2019yi sa\u011flam a\u00e7, HTTP\/3\u2019\u00fc iste\u011fe ba\u011fl\u0131 dene<\/a><ul><li><a href=\"#HTTP2yi_Nginxte_etkinlestirmek\"><span class=\"toc_number toc_depth_2\">4.1<\/span> HTTP\/2\u2019yi Nginx\u2019te etkinle\u015ftirmek<\/a><\/li><li><a href=\"#Deneysel_Nginxte_HTTP3_QUIC_etkinlestirmek\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Deneysel: Nginx\u2019te HTTP\/3 (QUIC) etkinle\u015ftirmek<\/a><\/li><\/ul><\/li><li><a href=\"#Cloudflare_tarafi_HTTP3u_ac_TLSi_saglam_tut_kenarda_sihir_yap\"><span class=\"toc_number toc_depth_1\">5<\/span> Cloudflare taraf\u0131: HTTP\/3\u2019\u00fc a\u00e7, TLS\u2019i sa\u011flam tut, kenarda sihir yap<\/a><ul><li><a href=\"#HTTP3u_Cloudflare_panelinden_etkinlestirmek\"><span class=\"toc_number toc_depth_2\">5.1<\/span> HTTP\/3\u2019\u00fc Cloudflare panelinden etkinle\u015ftirmek<\/a><\/li><li><a href=\"#WAF_ve_cache_ayarlarina_ufak_bir_dokunus\"><span class=\"toc_number toc_depth_2\">5.2<\/span> WAF ve cache ayarlar\u0131na ufak bir dokunu\u015f<\/a><\/li><\/ul><\/li><li><a href=\"#Test_ve_dogrulama_Hem_tarayicida_hem_terminalde_icimize_sinene_kadar\"><span class=\"toc_number toc_depth_1\">6<\/span> Test ve do\u011frulama: Hem taray\u0131c\u0131da hem terminalde i\u00e7imize sinene kadar<\/a><ul><li><a href=\"#Tarayiciyla_hizli_kontrol\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Taray\u0131c\u0131yla h\u0131zl\u0131 kontrol<\/a><\/li><li><a href=\"#curl_ile_komut_satirinda_protokolu_durtmek\"><span class=\"toc_number toc_depth_2\">6.2<\/span> curl ile komut sat\u0131r\u0131nda protokol\u00fc d\u00fcrtmek<\/a><\/li><li><a href=\"#Nginxden_emin_olmak_errorlog_ve_accesslog\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Nginx\u2019den emin olmak: error.log ve access.log<\/a><\/li><li><a href=\"#WordPressin_gozuyle_yonetici_ve_on_yuz\"><span class=\"toc_number toc_depth_2\">6.4<\/span> WordPress\u2019in g\u00f6z\u00fcyle: y\u00f6netici ve \u00f6n y\u00fcz<\/a><\/li><\/ul><\/li><li><a href=\"#Ufak_ama_etkili_dokunuslar_WordPress_onbellek_ve_kritik_yollar\"><span class=\"toc_number toc_depth_1\">7<\/span> Ufak ama etkili dokunu\u015flar: WordPress, \u00f6nbellek ve kritik yollar<\/a><ul><li><a href=\"#Karisik_icerik_mixed_content_ve_HTTPS_temizlikleri\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Kar\u0131\u015f\u0131k i\u00e7erik (mixed content) ve HTTPS temizlikleri<\/a><\/li><li><a href=\"#Onbellek_kenarda_ve_originde_ayni_sarkiyi_soylemek\"><span class=\"toc_number toc_depth_2\">7.2<\/span> \u00d6nbellek: kenarda ve origin\u2019de ayn\u0131 \u015fark\u0131y\u0131 s\u00f6ylemek<\/a><\/li><li><a href=\"#Guvenlik_katmani_hizla_kavga_etmeyen_koruma\"><span class=\"toc_number toc_depth_2\">7.3<\/span> G\u00fcvenlik katman\u0131: h\u0131zla kavga etmeyen koruma<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_adim_senaryolar_Uctan_uca_kisa_bir_kurgu\"><span class=\"toc_number toc_depth_1\">8<\/span> Ad\u0131m ad\u0131m senaryolar: U\u00e7tan uca k\u0131sa bir kurgu<\/a><ul><li><a href=\"#Senaryo_1_Cloudflare_onunde_NginxWordPress_hedef_HTTP2_HTTP3\"><span class=\"toc_number toc_depth_2\">8.1<\/span> Senaryo 1: Cloudflare \u00f6n\u00fcnde Nginx\/WordPress, hedef HTTP\/2 + HTTP\/3<\/a><\/li><li><a href=\"#Senaryo_2_Cloudflare_devre_disi_Nginxte_HTTP3u_dogrudan_denemek\"><span class=\"toc_number toc_depth_2\">8.2<\/span> Senaryo 2: Cloudflare devre d\u0131\u015f\u0131, Nginx\u2019te HTTP\/3\u2019\u00fc do\u011frudan denemek<\/a><\/li><\/ul><\/li><li><a href=\"#Sorun_giderme_Ufak_tefek_puruzleri_tatliya_baglamak\"><span class=\"toc_number toc_depth_1\">9<\/span> Sorun giderme: Ufak tefek p\u00fcr\u00fczleri tatl\u0131ya ba\u011flamak<\/a><ul><li><a href=\"#HTTP2_gorunmuyor_mu\"><span class=\"toc_number toc_depth_2\">9.1<\/span> HTTP\/2 g\u00f6r\u00fcnm\u00fcyor mu?<\/a><\/li><li><a href=\"#HTTP3_bir_var_bir_yok_mu\"><span class=\"toc_number toc_depth_2\">9.2<\/span> HTTP\/3 bir var bir yok mu?<\/a><\/li><li><a href=\"#WordPress_admin_yavasladi_mi\"><span class=\"toc_number toc_depth_2\">9.3<\/span> WordPress admin yava\u015flad\u0131 m\u0131?<\/a><\/li><li><a href=\"#Bonus_Ilerisi_icin_kucuk_bir_yol_haritasi\"><span class=\"toc_number toc_depth_2\">9.4<\/span> Bonus: \u0130lerisi i\u00e7in k\u00fc\u00e7\u00fck bir yol haritas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Kapanis_Hiz_sadece_sayi_degil_hissedilen_bir_akis\"><span class=\"toc_number toc_depth_1\">10<\/span> Kapan\u0131\u015f: H\u0131z sadece say\u0131 de\u011fil, hissedilen bir ak\u0131\u015f<\/a><\/li><\/ul><\/div>\n<h2 id=\"section-1\"><span id=\"Kahven_sogumadan_HTTP2_ve_HTTP3e_beraber_bir_yolculuk\">Kahven so\u011fumadan: HTTP\/2 ve HTTP\/3\u2019e beraber bir yolculuk<\/span><\/h2>\n<p>Hi\u00e7 ba\u015f\u0131n\u0131za geldi mi? Sabah ofise geldiniz, siteniz a\u00e7\u0131l\u0131yor ama sanki \u00fcst\u00fcne bir battaniye serilmi\u015f gibi a\u011f\u0131r. Trafik var, i\u00e7erik g\u00fczel, sunucu g\u00fc\u00e7l\u00fc; ama bir \u015fey eksik. Benim de bir g\u00fcn tam b\u00f6yle oldu. Bir yandan kahvemi kar\u0131\u015ft\u0131r\u0131rken, di\u011fer yandan a\u011f tabakas\u0131nda neyin t\u0131kand\u0131\u011f\u0131n\u0131 d\u00fc\u015f\u00fcnd\u00fcm. Sonra \u201cHadi \u015fu i\u015fi k\u00f6kten \u00e7\u00f6zelim\u201d dedim ve HTTP\/2 ile HTTP\/3\u2019\u00fcn kap\u0131s\u0131n\u0131 \u00e7ald\u0131m. O g\u00fcn \u201ctaray\u0131c\u0131 ile sunucunun ayn\u0131 dili daha ak\u0131c\u0131 konu\u015ftu\u011funda\u201d neler de\u011fi\u015fti\u011fini kendi g\u00f6z\u00fcmle g\u00f6rd\u00fcm.<\/p>\n<p>Bu yaz\u0131da, WordPress\u2019inizi Nginx \u00fczerinde ko\u015ftururken ve \u00f6n\u00fcnde Cloudflare duruyorken, HTTP\/2 ve HTTP\/3\u2019\u00fc u\u00e7tan uca nas\u0131l aya\u011fa kald\u0131rabilece\u011finizi anlataca\u011f\u0131m. Kafan\u0131z kar\u0131\u015fmas\u0131n; konuyu teknik detaylarla bo\u011fmadan, ad\u0131m ad\u0131m, \u00f6rneklerle gidece\u011fiz. Nginx taraf\u0131nda neleri a\u00e7man\u0131z gerekti\u011fini, Cloudflare panelinde hangi d\u00fc\u011fmelerin i\u015fimize yarad\u0131\u011f\u0131n\u0131, WordPress\u2019in bu de\u011fi\u015fiklikleri nas\u0131l kar\u015f\u0131lad\u0131\u011f\u0131n\u0131 ve en \u00f6nemlisi her \u015feyi nas\u0131l test edip do\u011frulayaca\u011f\u0131n\u0131z\u0131 konu\u015faca\u011f\u0131z. Sonunda, sayfalar\u0131n\u0131z\u0131n daha h\u0131zl\u0131 tepki verdi\u011fini hissetti\u011finizde, siz de benim gibi bir yudum kahveyi hak edeceksiniz.<\/p>\n<h2 id=\"section-2\"><span id=\"HTTP2_ve_HTTP3u_anlamak_Aradaki_farki_hissetmek\">HTTP\/2 ve HTTP\/3\u2019\u00fc anlamak: Aradaki fark\u0131 hissetmek<\/span><\/h2>\n<p>Mesela \u015f\u00f6yle d\u00fc\u015f\u00fcn\u00fcn: \u015eehrin bir ucundan \u00f6b\u00fcr ucuna giderken tek \u015feritli, \u0131\u015f\u0131kl\u0131 bir yol yerine, ayn\u0131 anda birden fazla araban\u0131n akabildi\u011fi, t\u00fcnellerle h\u0131zlanan bir hatt\u0131 kullan\u0131yorsunuz. HTTP\/2 tam olarak bu hissi veriyor. Tek bir ba\u011flant\u0131 \u00fczerinden ayn\u0131 anda birden fazla iste\u011fi ak\u0131tabilmek, bekleme s\u00fcrelerini k\u0131rp\u0131yor. \u00d6zellikle WordPress\u2019teki CSS, JS ve g\u00f6rsellerin bir arada geldi\u011fi anlarda nefes ald\u0131r\u0131yor.<\/p>\n<p>HTTP\/3 ise bir ad\u0131m daha cesur. Klasik TCP yerine UDP \u00fczerine kurulu QUIC protokol\u00fcn\u00fc kullan\u0131yor. Yani s\u0131k s\u0131k y\u00f6n de\u011fi\u015ftiren, bazen mobil, bazen Wi\u2011Fi ile dola\u015fan kullan\u0131c\u0131lar i\u00e7in ba\u011flant\u0131y\u0131 esnek tutuyor. Ba\u011flant\u0131 kopar gibi oldu\u011funda bile hemen aya\u011fa kalk\u0131yor ve sayfay\u0131 ak\u0131tmay\u0131 s\u00fcrd\u00fcr\u00fcyor. \u201cHangi biri daha h\u0131zl\u0131?\u201d diye merak etmek normal, ama pratikte as\u0131l kazan\u00e7; daha az beklemek, daha az t\u0131kanmak ve kullan\u0131c\u0131ya daha <strong>ak\u0131c\u0131 bir deneyim<\/strong> sunmak.<\/p>\n<p>Burada k\u00fc\u00e7\u00fck bir not: Cloudflare kullan\u0131c\u0131 ile edge aras\u0131nda HTTP\/3 konu\u015fabiliyor. Edge ile sizin sunucunuz aras\u0131nda ise \u00e7o\u011fu senaryoda HTTP\/2 ya da HTTP\/1.1 devrede. Bu k\u00f6t\u00fc bir \u015fey de\u011fil; taray\u0131c\u0131 taraf\u0131nda kazan\u0131lan ak\u0131\u015fkanl\u0131k zaten hissediliyor. Ama isterseniz, do\u011frudan Nginx\u2019te deneysel HTTP\/3\u2019\u00fc a\u00e7\u0131p kendi testlerinizi de yapabilirsiniz. Birazdan hepsini g\u00f6sterece\u011fim.<\/p>\n<h2 id=\"section-3\"><span id=\"Hazirlik_WordPress_Nginx_ve_Cloudflarei_ayni_masaya_oturtmak\">Haz\u0131rl\u0131k: WordPress, Nginx ve Cloudflare\u2019i ayn\u0131 masaya oturtmak<\/span><\/h2>\n<p>\u00d6nce k\u00fc\u00e7\u00fck bir haz\u0131rl\u0131k listesi yapal\u0131m, ama bunu bir liste gibi de\u011fil, \u201cmutfa\u011fa girmeden \u00f6nce malzemeye g\u00f6z atmak\u201d gibi d\u00fc\u015f\u00fcn\u00fcn. WordPress\u2019iniz Nginx \u00fczerinde ko\u015fuyor ve sitenize ge\u00e7erli bir TLS sertifikas\u0131 ile hizmet veriyorsunuz. Sertifika i\u015fi zaten h\u0131z ve g\u00fcven i\u00e7in bamba\u015fka bir d\u00fcnya; Nginx taraf\u0131nda TLS 1.3, iyi kurgulanm\u0131\u015f \u015fifre tak\u0131mlar\u0131 ve OCSP stapling her zaman dostunuz. Bu konular\u0131 daha ayr\u0131nt\u0131l\u0131 kurmak isterseniz, \u015fu rehberdeki pratik ad\u0131mlar \u00e7ok i\u015f g\u00f6r\u00fcyor: <a href=\"https:\/\/www.dchost.com\/blog\/nginxte-tls-1-3-ocsp-stapling-ve-brotli-nasil-kurulur-hizli-ve-guvenli-httpsnin-sicacik-rehberi\/\">Nginx\u2019te TLS 1.3, OCSP Stapling ve Brotli Nas\u0131l Kurulur? H\u0131zl\u0131 ve G\u00fcvenli HTTPS\u2019nin S\u0131cac\u0131k Rehberi<\/a>.<\/p>\n<p>Cloudflare taraf\u0131nda alan ad\u0131n\u0131z ekli, DNS\u2019i Cloudflare\u2019e teslim etmi\u015f durumdas\u0131n\u0131z. SSL\/TLS modunu <strong>Full (strict)<\/strong> kullanman\u0131z\u0131 t\u00fcm kalbimle \u00f6neririm; b\u00f6ylece Cloudflare ile origin sunucu aras\u0131nda da ger\u00e7ekten \u015fifreli ve do\u011frulanm\u0131\u015f bir hat kurars\u0131n\u0131z. WordPress taraf\u0131nda ise \u00e7ok \u00f6zel bir \u015fey yapman\u0131za gerek yok, ama birazdan bahsedece\u011fim ufak dokunu\u015flar i\u015fleri p\u00fcr\u00fczs\u00fczle\u015ftiriyor: kar\u0131\u015f\u0131k i\u00e7erik (mixed content) temizli\u011fi, \u00f6nbellek eklentisi ayarlar\u0131 ve y\u00f6netici trafi\u011finin ak\u0131ll\u0131ca kurgulanmas\u0131 gibi.<\/p>\n<h2 id=\"section-4\"><span id=\"Nginx_tarafi_HTTP2yi_saglam_ac_HTTP3u_istege_bagli_dene\">Nginx taraf\u0131: HTTP\/2\u2019yi sa\u011flam a\u00e7, HTTP\/3\u2019\u00fc iste\u011fe ba\u011fl\u0131 dene<\/span><\/h2>\n<h3><span id=\"HTTP2yi_Nginxte_etkinlestirmek\">HTTP\/2\u2019yi Nginx\u2019te etkinle\u015ftirmek<\/span><\/h3>\n<p>Nginx\u2019te HTTP\/2 a\u00e7mak, do\u011fru yere tek bir anahtar eklemek kadar kolay. \u00d6nemli olan, \u201c443\u201d\u2019te SSL ile birlikte \u201chttp2\u201d parametresini kullanmak. Bir WordPress sanal host\u2019u d\u00fc\u015f\u00fcnelim; \u015fu yap\u0131 ta\u015flar\u0131 i\u015finizi g\u00f6r\u00fcr:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 443 ssl http2;\n    server_name example.com www.example.com;\n\n    root \/var\/www\/example.com\/public;\n    index index.php index.html;\n\n    ssl_certificate     \/etc\/letsencrypt\/live\/example.com\/fullchain.pem;\n    ssl_certificate_key \/etc\/letsencrypt\/live\/example.com\/privkey.pem;\n\n    # TLS ve s\u0131k\u0131\u015ft\u0131rma gibi ince ayarlar i\u00e7in ilgili rehber:\n    # (TLS 1.3, OCSP stapling, Brotli vs.)\n\n    location \/ {\n        try_files $uri $uri\/ \/index.php?$args;\n    }\n\n    location ~ .php$ {\n        include fastcgi_params;\n        fastcgi_pass unix:\/run\/php\/php8.2-fpm.sock;\n        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n        fastcgi_read_timeout 60s;\n    }\n}\n<\/code><\/pre>\n<p>Bu kadar. Tabii, sertifikan\u0131z do\u011fru yerde, PHP\u2011FPM soketiniz do\u011fru yolda olmal\u0131. Bu ayarlarla Nginx gelen HTTPS taleplerine HTTP\/2 \u00fczerinden yan\u0131t verecek. Cloudflare origin ile konu\u015furken \u00e7o\u011fu durumda HTTP\/2 kullanmay\u0131 tercih ediyor, ama bunu \u201czorunlu\u201d bir anahtarla y\u00f6netmiyorsunuz; \u00f6nemli olan origin\u2019in HTTP\/2\u2019yi destekliyor olmas\u0131. Nginx\u2019in HTTP\/2 mod\u00fcl dok\u00fcmantasyonuna g\u00f6z atmak isterseniz, resmi kaynaklar net anlat\u0131yor: <a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_v2_module.html\" rel=\"nofollow noopener\" target=\"_blank\">Nginx HTTP\/2 mod\u00fcl dok\u00fcman\u0131<\/a>.<\/p>\n<h3><span id=\"Deneysel_Nginxte_HTTP3_QUIC_etkinlestirmek\">Deneysel: Nginx\u2019te HTTP\/3 (QUIC) etkinle\u015ftirmek<\/span><\/h3>\n<p>\u015eimdi gelelim merak uyand\u0131ran tarafa. Nginx, yeni s\u00fcr\u00fcmleriyle HTTP\/3\u2019\u00fc deneysel olarak destekliyor. Bu, taray\u0131c\u0131 ile do\u011frudan sizin sunucunuz aras\u0131nda HTTP\/3 konu\u015fmak demek. E\u011fer Cloudflare\u2019i kapat\u0131p do\u011frudan origin\u2019e test etmek, ya da Cloudflare devre d\u0131\u015f\u0131yken performans \u00f6l\u00e7mek istiyorsan\u0131z, a\u015fa\u011f\u0131daki yap\u0131 i\u015f g\u00f6r\u00fcr. Bunun i\u00e7in Nginx\u2019in QUIC\/HTTP\/3 mod\u00fclleriyle derlenmi\u015f oldu\u011fundan emin olun.<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    # HTTP\/2 hatt\u0131 (TLS \u00fczerinden)\n    listen 443 ssl http2;\n\n    # HTTP\/3 hatt\u0131 (QUIC\/UDP \u00fczerinden)\n    listen 443 quic reuseport;\n\n    server_name example.com www.example.com;\n\n    ssl_certificate     \/etc\/letsencrypt\/live\/example.com\/fullchain.pem;\n    ssl_certificate_key \/etc\/letsencrypt\/live\/example.com\/privkey.pem;\n\n    # HTTP\/3 i\u00e7in TLS 1.3 \u015fart; ALPN otomatik ayarlan\u0131r\n    ssl_protocols TLSv1.3;\n\n    # Taray\u0131c\u0131ya HTTP\/3 alternatifi sun\n    add_header Alt-Svc 'h3=&quot;:443&quot;; ma=86400; persist=1';\n\n    root \/var\/www\/example.com\/public;\n    index index.php index.html;\n\n    location \/ {\n        try_files $uri $uri\/ \/index.php?$args;\n    }\n\n    location ~ .php$ {\n        include fastcgi_params;\n        fastcgi_pass unix:\/run\/php\/php8.2-fpm.sock;\n        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n    }\n}\n<\/code><\/pre>\n<p>Bir not daha: Cloudflare arada oldu\u011funda, taray\u0131c\u0131 ile Cloudflare edge\u2019i HTTP\/3 konu\u015fur, Cloudflare ile origin aras\u0131 ise genellikle HTTP\/2\/HTTP\/1.1 olur. Yani yukar\u0131daki HTTP\/3 ayar\u0131, daha \u00e7ok Cloudflare\u2019siz do\u011frudan testler veya ilerideki olas\u0131 senaryolara haz\u0131rl\u0131k i\u00e7indir. HTTP\/3 mod\u00fcl\u00fc ve direktifler i\u00e7in resmi dok\u00fcmana g\u00f6z atabilirsiniz: <a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_v3_module.html\" rel=\"nofollow noopener\" target=\"_blank\">Nginx HTTP\/3 (QUIC) mod\u00fcl dok\u00fcman\u0131<\/a>.<\/p>\n<h2 id=\"section-5\"><span id=\"Cloudflare_tarafi_HTTP3u_ac_TLSi_saglam_tut_kenarda_sihir_yap\">Cloudflare taraf\u0131: HTTP\/3\u2019\u00fc a\u00e7, TLS\u2019i sa\u011flam tut, kenarda sihir yap<\/span><\/h2>\n<h3><span id=\"HTTP3u_Cloudflare_panelinden_etkinlestirmek\">HTTP\/3\u2019\u00fc Cloudflare panelinden etkinle\u015ftirmek<\/span><\/h3>\n<p>Cloudflare\u2019da HTTP\/3 a\u00e7ma k\u0131sm\u0131 \u00e7ok basit. Panelde ilgili alan ad\u0131n\u0131 se\u00e7tikten sonra Network b\u00f6l\u00fcm\u00fcnde \u201cHTTP\/3 (with QUIC)\u201d anahtar\u0131n\u0131 etkinle\u015ftirmeniz yeterli. B\u00f6ylece taray\u0131c\u0131 ile Cloudflare edge\u2019i aras\u0131nda HTTP\/3 konu\u015fulmaya ba\u015flar. Kullan\u0131c\u0131, \u00f6zellikle mobil a\u011flarda, daha seri bir y\u00fcklenme hisseder. Bu anahtar\u0131n yan\u0131nda kimi zaman 0\u2011RTT veya benzeri se\u00e7enekler de g\u00f6r\u00fcrs\u00fcn\u00fcz; hepsini ayn\u0131 anda a\u00e7mak yerine, birer birer deneyip \u00f6l\u00e7erek gitmenizi \u00f6neririm. Cloudflare\u2019\u0131n konuya dair detayl\u0131 yaz\u0131lar\u0131 da \u201cbu nas\u0131l \u00e7al\u0131\u015f\u0131yor?\u201d merak\u0131n\u0131 tatmin eder: <a href=\"https:\/\/curl.se\/docs\/http3.html\" rel=\"nofollow noopener\" target=\"_blank\">curl ile HTTP\/3 testi<\/a> gibi pratik kaynaklar ve Cloudflare\u2019\u0131n teknik payla\u015f\u0131mlar\u0131 bak\u0131\u015f a\u00e7\u0131s\u0131 kazand\u0131r\u0131r.<\/p>\n<p>TLS ayarlar\u0131nda, \u201cAlways Use HTTPS\u201d ve \u201cAutomatic HTTPS Rewrites\u201d genellikle i\u015fleri kolayla\u015ft\u0131r\u0131r. Ama WordPress\u2019te eski i\u00e7eriklerde h\u00e2l\u00e2 http ile ba\u015flayan ba\u011flant\u0131lar\u0131n\u0131z varsa, \u00f6nce bunlar\u0131 temizlemek iyi olur. \u00c7\u00fcnk\u00fc bu se\u00e7enekler bazen sihirli g\u00f6r\u00fcnse de, k\u00f6kten bir d\u00fczeltmenin yerini tutmaz. Origin taraf\u0131nda \u201cFull (strict)\u201d ile sa\u011flam bir zincir kurdu\u011funuzda i\u00e7iniz rahat eder.<\/p>\n<h3><span id=\"WAF_ve_cache_ayarlarina_ufak_bir_dokunus\">WAF ve cache ayarlar\u0131na ufak bir dokunu\u015f<\/span><\/h3>\n<p>Performans ne kadar g\u00fczel olursa olsun, WordPress\u2019i bot\u2019lar\u0131n y\u0131pratmas\u0131na izin vermek istemezsiniz. Cloudflare\u2019\u0131n WAF kurallar\u0131 ve oran s\u0131n\u0131rlama (rate limiting) ayarlar\u0131 burada hayat kurtar\u0131yor. E\u011fer bu konuyu daha \u00f6nce didiklemek istiyorsan\u0131z, \u015fu rehber \u00e7ok i\u015fe yar\u0131yor: <a href=\"https:\/\/www.dchost.com\/blog\/cloudflare-waf-kurallari-ve-oran-sinirlama-ile-wordpressi-botlardan-nasil-korursun\/\">Cloudflare WAF Kurallar\u0131 ve Oran S\u0131n\u0131rlama ile WordPress\u2019i Bot\u2019lardan Nas\u0131l Korursun?<\/a>. Ayr\u0131ca kenar \u00f6nbellekleme kurallar\u0131yla (Edge Rules) birlikte HTTP\/2\/HTTP\/3 hatt\u0131n\u0131n verdi\u011fi h\u0131z birle\u015fince, sayfalar\u0131n\u0131z adeta \u201ctak\u0131lmadan akan\u201d bir hal al\u0131yor. \u0130leri seviye kurallara ilham ararsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/cdn-onbellekleme-cache-control-ve-edge-kurallari-wordpress-ve-woocommercede-tam-isabet-ayarlar\/\">CDN \u00d6nbellekleme, Cache\u2011Control ve Edge Kurallar\u0131<\/a> yaz\u0131s\u0131ndaki \u00f6rnekler tam yerine oturuyor.<\/p>\n<h2 id=\"section-6\"><span id=\"Test_ve_dogrulama_Hem_tarayicida_hem_terminalde_icimize_sinene_kadar\">Test ve do\u011frulama: Hem taray\u0131c\u0131da hem terminalde i\u00e7imize sinene kadar<\/span><\/h2>\n<h3><span id=\"Tarayiciyla_hizli_kontrol\">Taray\u0131c\u0131yla h\u0131zl\u0131 kontrol<\/span><\/h3>\n<p>\u0130lk provay\u0131 taray\u0131c\u0131da yapmay\u0131 seviyorum. Geli\u015ftirici ara\u00e7lar\u0131n\u0131 a\u00e7\u0131n, Network sekmesinde isteklere bak\u0131n. \u201cProtocol\u201d veya benzeri bir s\u00fctunda \u201ch2\u201d, \u201ch3\u201d gibi ibareleri g\u00f6r\u00fcrs\u00fcn\u00fcz. Cloudflare a\u00e7\u0131kken kullan\u0131c\u0131 taraf\u0131nda \u201ch3\u201d ibaresi belirdi\u011finde tebess\u00fcm etmek serbest. G\u00f6rm\u00fcyorsan\u0131z panik yok; bazen taray\u0131c\u0131lar deneme\u2011yan\u0131lmayla protokol se\u00e7er, \u00f6nbelle\u011fi temizleyip bir daha deneyin.<\/p>\n<h3><span id=\"curl_ile_komut_satirinda_protokolu_durtmek\">curl ile komut sat\u0131r\u0131nda protokol\u00fc d\u00fcrtmek<\/span><\/h3>\n<p>curl, bu i\u015fin cep telefonu. HTTP\/2 i\u00e7in:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">curl -I --http2 https:\/\/example.com\n<\/code><\/pre>\n<p>Yan\u0131tta \u201cHTTP\/2 200\u201d g\u00f6r\u00fcrseniz tamamd\u0131r. HTTP\/3 i\u00e7in curl s\u00fcr\u00fcm\u00fcn\u00fcz\u00fcn HTTP\/3 destekli oldu\u011fundan emin olun; sonra:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">curl -I --http3 https:\/\/example.com\n<\/code><\/pre>\n<p>Yan\u0131tta \u201cHTTP\/3 200\u201d g\u00f6rmek, taray\u0131c\u0131n\u0131n g\u00f6rece\u011fi manzaran\u0131n bir \u00f6zetidir. curl ile HTTP\/3 hakk\u0131nda k\u0131sa ama net bir sayfay\u0131 merak edenler i\u00e7in: <a href=\"https:\/\/curl.se\/docs\/http3.html\" rel=\"nofollow noopener\" target=\"_blank\">curl HTTP\/3 rehberi<\/a>.<\/p>\n<h3><span id=\"Nginxden_emin_olmak_errorlog_ve_accesslog\">Nginx\u2019den emin olmak: error.log ve access.log<\/span><\/h3>\n<p>Origin\u2019in HTTP\/2\u2019ye a\u00e7\u0131k oldu\u011funu teyit etmek i\u00e7in Nginx loglar\u0131na bakmak iyi gelir. Eri\u015fim g\u00fcnl\u00fcklerinde \u201cHTTP\/2\u201d notlar\u0131n\u0131 ve ba\u011flant\u0131 \u00f6zetlerini g\u00f6rebilirsiniz. Cloudflare aradayken origin\u2019in HTTP\/3 konu\u015fmas\u0131n\u0131 beklemeyin; kullan\u0131c\u0131 edge\u2019e HTTP\/3 ile gelirken, edge sizinle \u00e7o\u011funlukla HTTP\/2 \u00fczerinden konu\u015fur. Bu ayr\u0131m normaldir.<\/p>\n<h3><span id=\"WordPressin_gozuyle_yonetici_ve_on_yuz\">WordPress\u2019in g\u00f6z\u00fcyle: y\u00f6netici ve \u00f6n y\u00fcz<\/span><\/h3>\n<p>WordPress admin paneli bazen \u00f6nbellek ve g\u00fcvenlik katmanlar\u0131na hassas olabilir. Admin trafi\u011fini Cloudflare\u2019da \u00f6nbellek d\u0131\u015f\u0131 b\u0131rakmak, robot kurallar\u0131n\u0131 da abartmamak iyi bir denge sa\u011flar. \u00d6ny\u00fczde ise tam sayfa \u00f6nbellekleme ile HTTP\/2\/HTTP\/3\u2019\u00fcn sa\u011flad\u0131\u011f\u0131 ba\u011flant\u0131 avantaj\u0131 birle\u015fince sonu\u00e7 ger\u00e7ekten tatl\u0131 oluyor. \u201cBu i\u015fi nas\u0131l kurar\u0131m?\u201d derseniz, ad\u0131m ad\u0131m \u00f6rnekleriyle \u015furada anlatt\u0131m: <a href=\"https:\/\/www.dchost.com\/blog\/wordpresste-tam-sayfa-onbellekleme-nasil-kurulur-nginx-fastcgi-cache-varnish-ve-litespeed-cache-ile-woocommercee-nazikce-dokunmak\/\">WordPress\u2019te Tam Sayfa \u00d6nbellekleme Nas\u0131l Kurulur?<\/a>.<\/p>\n<h2 id=\"section-7\"><span id=\"Ufak_ama_etkili_dokunuslar_WordPress_onbellek_ve_kritik_yollar\">Ufak ama etkili dokunu\u015flar: WordPress, \u00f6nbellek ve kritik yollar<\/span><\/h2>\n<h3><span id=\"Karisik_icerik_mixed_content_ve_HTTPS_temizlikleri\">Kar\u0131\u015f\u0131k i\u00e7erik (mixed content) ve HTTPS temizlikleri<\/span><\/h3>\n<p>HTTP\/2\/HTTP\/3 ne kadar g\u00fczel olursa olsun, sayfan\u0131zda http ile ba\u015flayan g\u00f6rseller veya script\u2019ler varsa taray\u0131c\u0131 huzursuz olur. Temizlemenin en garantili yolu; veritaban\u0131nda eski adresleri https ile g\u00fcncellemek ve tema ayarlar\u0131nda kalan k\u0131r\u0131nt\u0131lar\u0131 bulup d\u00fczeltmek. Baz\u0131 eklentiler ge\u00e7ici \u00e7\u00f6z\u00fcmler sunsa da, k\u00f6kten temizledi\u011finizde bir daha u\u011fra\u015fmazs\u0131n\u0131z.<\/p>\n<h3><span id=\"Onbellek_kenarda_ve_originde_ayni_sarkiyi_soylemek\">\u00d6nbellek: kenarda ve origin\u2019de ayn\u0131 \u015fark\u0131y\u0131 s\u00f6ylemek<\/span><\/h3>\n<p>Cloudflare \u00fczerinde statik dosyalar\u0131 g\u00f6n\u00fcl rahatl\u0131\u011f\u0131yla \u00f6nbelle\u011fe alabilirsiniz. WordPress\u2019te ise sayfa \u00f6nbelle\u011fi, HTML\u2019nin \u201chaz\u0131r\u201d halde beklemesini sa\u011flar. Nginx FastCGI Cache ile \u00e7ok hafif ve etkili bir yap\u0131 kurabilirsiniz. WooCommerce gibi dinamik sepeti olan projelerde, belirli \u00e7erezleri g\u00f6z ard\u0131 ederek, sepet ve \u00f6deme ad\u0131mlar\u0131n\u0131 \u00f6nbellek d\u0131\u015f\u0131nda tutmak gerekir. Kenar kurallar\u0131 ile bu dengeyi rahat\u00e7a kurabiliyorsunuz; bir bak\u0131\u015f daha isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/cdn-onbellekleme-cache-control-ve-edge-kurallari-wordpress-ve-woocommercede-tam-isabet-ayarlar\/\">Edge kurallar\u0131yla tam isabet ayarlar<\/a> b\u00f6l\u00fcm\u00fcndeki \u00f6rnek ak\u0131\u015flar tam buna hizmet eder.<\/p>\n<h3><span id=\"Guvenlik_katmani_hizla_kavga_etmeyen_koruma\">G\u00fcvenlik katman\u0131: h\u0131zla kavga etmeyen koruma<\/span><\/h3>\n<p>WAF kurallar\u0131n\u0131 \u00e7ok s\u0131k\u0131la\u015ft\u0131r\u0131p trafi\u011fi bo\u011fmak yerine, WordPress\u2019e musallat olan k\u00f6t\u00fc niyetli ak\u0131\u015flar\u0131 kibarca d\u0131\u015far\u0131da b\u0131rakmak daha sa\u011fl\u0131kl\u0131. Bot\u2019lar\u0131 sakinle\u015ftiren e\u015fik de\u011ferleri, admin giri\u015f denemelerini s\u0131n\u0131rlayan kurallar ve \u00fclke bazl\u0131 ak\u0131ll\u0131 filtreler \u00e7o\u011fu projede \u201cg\u00fcr\u00fclt\u00fcy\u00fc\u201d kesiyor. Bu d\u00fczeni kurarken performans da elinizle art\u0131yor; \u00e7\u00fcnk\u00fc sunucu gereksiz i\u015flerle yorulmuyor. Bu dengeyi kurman\u0131n pratik bir hik\u00e2yesi i\u00e7in: <a href=\"https:\/\/www.dchost.com\/blog\/waf-ve-bot-korumasi-cloudflare-modsecurity-ve-fail2bani-ayni-masada-baristirmanin-sicacik-hikayesi\/\">WAF ve Bot Korumas\u0131: Cloudflare, ModSecurity ve Fail2ban\u2019\u0131 Ayn\u0131 Masada Bar\u0131\u015ft\u0131rmak<\/a>.<\/p>\n<h2 id=\"section-8\"><span id=\"Adim_adim_senaryolar_Uctan_uca_kisa_bir_kurgu\">Ad\u0131m ad\u0131m senaryolar: U\u00e7tan uca k\u0131sa bir kurgu<\/span><\/h2>\n<h3><span id=\"Senaryo_1_Cloudflare_onunde_NginxWordPress_hedef_HTTP2_HTTP3\">Senaryo 1: Cloudflare \u00f6n\u00fcnde Nginx\/WordPress, hedef HTTP\/2 + HTTP\/3<\/span><\/h3>\n<p>\u00d6nce Nginx\u2019te \u201clisten 443 ssl http2;\u201d ile HTTP\/2\u2019yi a\u00e7\u0131yorsunuz. TLS 1.3 ve OCSP stapling gibi h\u0131z\/g\u00fcven ayarlar\u0131n\u0131 tamaml\u0131yorsunuz. Cloudflare panelinde HTTP\/3 anahtar\u0131n\u0131 etkinle\u015ftiriyorsunuz. WordPress\u2019te kar\u0131\u015f\u0131k i\u00e7erikleri temizliyor, \u00f6nbelle\u011fi ak\u0131ll\u0131 kurallarla devreye al\u0131yorsunuz. Taray\u0131c\u0131 DevTools\u2019ta \u201ch3\u201d g\u00f6r\u00fcnd\u00fc\u011f\u00fcnde, terminalde de \u201ccurl -I &#8211;http3\u201d komutuyla do\u011fruluyorsunuz. Origin log\u2019lar\u0131nda HTTP\/2 sat\u0131rlar\u0131 g\u00f6r\u00fcl\u00fcyor; bu normal. Sonra sayfa ge\u00e7i\u015flerine bakt\u0131\u011f\u0131n\u0131zda, \u00f6zellikle mobilde, daha ak\u0131c\u0131 bir deneyim hissetmeye ba\u015fl\u0131yorsunuz.<\/p>\n<h3><span id=\"Senaryo_2_Cloudflare_devre_disi_Nginxte_HTTP3u_dogrudan_denemek\">Senaryo 2: Cloudflare devre d\u0131\u015f\u0131, Nginx\u2019te HTTP\/3\u2019\u00fc do\u011frudan denemek<\/span><\/h3>\n<p>DNS\u2019i ge\u00e7ici olarak do\u011frudan origin\u2019e i\u015faretleyip Nginx\u2019te \u201clisten 443 quic reuseport;\u201d ve Alt\u2011Svc ba\u015fl\u0131\u011f\u0131n\u0131 ekliyorsunuz. curl ve modern taray\u0131c\u0131larla HTTP\/3\u2019\u00fc do\u011fruluyorsunuz. Bu senaryo, \u00f6l\u00e7\u00fcm yapmak, k\u0131yaslamay\u0131 g\u00f6z\u00fcn\u00fczle g\u00f6rmek ve \u201cacaba a\u011f ko\u015fullar\u0131mda ne fark var?\u201d sorusuna cevap aramak i\u00e7in g\u00fczel. Yeniden Cloudflare\u2019i devreye ald\u0131\u011f\u0131n\u0131zda, kullan\u0131c\u0131\u2011edge aras\u0131 HTTP\/3 zaten sizin ad\u0131n\u0131za \u00e7al\u0131\u015fmay\u0131 s\u00fcrd\u00fcr\u00fcyor.<\/p>\n<h2 id=\"section-9\"><span id=\"Sorun_giderme_Ufak_tefek_puruzleri_tatliya_baglamak\">Sorun giderme: Ufak tefek p\u00fcr\u00fczleri tatl\u0131ya ba\u011flamak<\/span><\/h2>\n<h3><span id=\"HTTP2_gorunmuyor_mu\">HTTP\/2 g\u00f6r\u00fcnm\u00fcyor mu?<\/span><\/h3>\n<p>\u00c7o\u011fu zaman SSL b\u00f6l\u00fcm\u00fcnde \u201chttp2\u201d parametresinin unutulmas\u0131 y\u00fcz\u00fcnden olur. Nginx\u2019i yeniden y\u00fckledikten (reload) sonra h\u00e2l\u00e2 sonu\u00e7 alam\u0131yorsan\u0131z, ara katmanda bir ters vekil (proxy) veya g\u00fcvenlik duvar\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol edin. Cloudflare kullan\u0131yorsan\u0131z, origin\u2019in HTTP\/2 deste\u011fi olsa bile eri\u015fim g\u00fcnl\u00fcklerinde HTTP\/1.1 sat\u0131rlar\u0131 da g\u00f6rebilirsiniz; bu anl\u0131k ko\u015fullar ve ba\u011flant\u0131 tercihleriyle ilgilidir.<\/p>\n<h3><span id=\"HTTP3_bir_var_bir_yok_mu\">HTTP\/3 bir var bir yok mu?<\/span><\/h3>\n<p>Taray\u0131c\u0131lar ba\u011flant\u0131 ko\u015fullar\u0131na g\u00f6re protokol se\u00e7er. \u0130lk istekte HTTP\/2, sonra HTTP\/3\u2019e ge\u00e7i\u015f gibi davran\u0131\u015flar normaldir. Cloudflare\u2019da HTTP\/3 anahtar\u0131n\u0131n a\u00e7\u0131k oldu\u011fundan, taray\u0131c\u0131n\u0131z\u0131n g\u00fcncel oldu\u011fundan ve kurumsal a\u011f\u0131n\u0131zda UDP\/443\u2019e izin verildi\u011finden emin olun. Nginx\u2019te do\u011frudan HTTP\/3 deniyorsan\u0131z, s\u00fcr\u00fcm ve derleme se\u00e7eneklerinin do\u011fru oldu\u011fundan emin olmak \u015fartt\u0131r.<\/p>\n<h3><span id=\"WordPress_admin_yavasladi_mi\">WordPress admin yava\u015flad\u0131 m\u0131?<\/span><\/h3>\n<p>Admin i\u00e7in \u00f6nbellek d\u0131\u015f\u0131nda kalacak kurallar tan\u0131mlay\u0131n. Cloudflare \u00fczerinde \u201c\/wp-admin\/\u201d ve \u201c\/wp-login.php\u201d i\u00e7in \u00f6nbellek devre d\u0131\u015f\u0131 kalmal\u0131. Baz\u0131 g\u00fcvenlik eklentileri a\u015f\u0131r\u0131 korumac\u0131 davran\u0131p her istekte ekstra gecikme yaratabilir; ayarlar\u0131n\u0131 sadele\u015ftirip tekrar deneyin. Kalan yava\u015fl\u0131k genelde veritaban\u0131 sorgular\u0131d\u0131r; onu da ba\u015fka bir g\u00fcn uzun uzun konu\u015furuz.<\/p>\n<h3><span id=\"Bonus_Ilerisi_icin_kucuk_bir_yol_haritasi\">Bonus: \u0130lerisi i\u00e7in k\u00fc\u00e7\u00fck bir yol haritas\u0131<\/span><\/h3>\n<p>HTTP\/2\/HTTP\/3 raylar\u0131n\u0131 d\u00f6\u015fedikten sonra, sunucu optimizasyonlar\u0131yla fark\u0131 katlayabilirsiniz. \u00d6rne\u011fin PHP\u2011FPM, OPcache ve kuyruk sistemlerini bir arada ele alan \u015fu rehber \u00fcretim ortamlar\u0131nda \u00e7ok i\u015f g\u00f6r\u00fcr: <a href=\"https:\/\/www.dchost.com\/blog\/laravel-prod-ortam-optimizasyonu-nasil-yapilir-php%e2%80%91fpm-opcache-octane-queue-horizon-ve-redisi-el-ele-calistirmak\/\">Prod ortam optimizasyonu pratikleri<\/a>. Her ne kadar ba\u015fl\u0131\u011f\u0131 Laravel dese de, prensiplerin \u00f6nemli bir k\u0131sm\u0131 WordPress i\u00e7in de yol g\u00f6sterici.<\/p>\n<h2 id=\"section-10\"><span id=\"Kapanis_Hiz_sadece_sayi_degil_hissedilen_bir_akis\">Kapan\u0131\u015f: H\u0131z sadece say\u0131 de\u011fil, hissedilen bir ak\u0131\u015f<\/span><\/h2>\n<p>Bug\u00fcn birlikte, Nginx ve Cloudflare taraf\u0131nda HTTP\/2 ve HTTP\/3\u2019\u00fc a\u00e7\u0131p, WordPress\u2019in de bu ak\u0131\u015fa zarif\u00e7e kat\u0131lmas\u0131n\u0131 sa\u011flad\u0131k. Asl\u0131nda yapt\u0131\u011f\u0131m\u0131z \u015fey basit: taray\u0131c\u0131 ile sunucu aras\u0131ndaki konu\u015fmay\u0131 daha ak\u0131c\u0131, daha esnek ve daha az bekleyen bir hale getirmek. K\u00fc\u00e7\u00fcc\u00fck dokunu\u015flar\u0131n sayfa hissiyat\u0131n\u0131 nas\u0131l de\u011fi\u015ftirdi\u011fini g\u00f6rmek her zaman keyif veriyor. \u00d6zellikle mobilde, d\u00fc\u015f\u00fck kaliteli a\u011flarda ve yo\u011fun trafik anlar\u0131nda fark daha belirgin hissediliyor.<\/p>\n<p>Son tavsiye: De\u011fi\u015fiklikleri tek seferde de\u011fil, ad\u0131m ad\u0131m yap\u0131n. \u00d6nce Nginx\u2019te HTTP\/2\u2019yi a\u00e7\u0131n, sonra Cloudflare\u2019da HTTP\/3\u2019\u00fc etkinle\u015ftirin, ard\u0131ndan WordPress\u2019te \u00f6nbellek ve kar\u0131\u015f\u0131k i\u00e7erik temizliklerini tamamlay\u0131n. Her ad\u0131m sonras\u0131 taray\u0131c\u0131 ve curl ile testi ihmal etmeyin. \u0130\u00e7inize sinmeyen bir \u015fey olursa geri almas\u0131 daha kolay olur. Umar\u0131m bu rehber, elinizi korkak al\u0131\u015ft\u0131rmadan deneme yapabilmeniz i\u00e7in yeterince s\u0131cak ve anla\u015f\u0131l\u0131r olmu\u015ftur. Bir dahaki yaz\u0131da daha ince ayarlarla, belki de farkl\u0131 senaryolarda tekrar bulu\u015furuz; \u015fimdilik kahve molas\u0131 serbest.<\/p>\n<hr>\n<p>Kaynaklar\u0131na g\u00f6z atmak isteyenlere not: Nginx dok\u00fcmanlar\u0131, HTTP\/2 ve HTTP\/3 mod\u00fcllerini sade anlat\u0131yor. Merakl\u0131s\u0131na ba\u011flant\u0131lar\u0131 b\u0131rak\u0131yorum: <a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_v2_module.html\" rel=\"nofollow noopener\" target=\"_blank\">Nginx HTTP\/2 mod\u00fcl\u00fc<\/a> ve <a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_v3_module.html\" rel=\"nofollow noopener\" target=\"_blank\">Nginx HTTP\/3 (QUIC) mod\u00fcl\u00fc<\/a>. Ayr\u0131ca terminalde h\u0131zl\u0131 denemeler i\u00e7in <a href=\"https:\/\/curl.se\/docs\/http3.html\" rel=\"nofollow noopener\" target=\"_blank\">curl HTTP\/3 sayfas\u0131<\/a> pratik ipu\u00e7lar\u0131 sunuyor.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Kahven so\u011fumadan: HTTP\/2 ve HTTP\/3\u2019e beraber bir yolculuk2 HTTP\/2 ve HTTP\/3\u2019\u00fc anlamak: Aradaki fark\u0131 hissetmek3 Haz\u0131rl\u0131k: WordPress, Nginx ve Cloudflare\u2019i ayn\u0131 masaya oturtmak4 Nginx taraf\u0131: HTTP\/2\u2019yi sa\u011flam a\u00e7, HTTP\/3\u2019\u00fc iste\u011fe ba\u011fl\u0131 dene4.1 HTTP\/2\u2019yi Nginx\u2019te etkinle\u015ftirmek4.2 Deneysel: Nginx\u2019te HTTP\/3 (QUIC) etkinle\u015ftirmek5 Cloudflare taraf\u0131: HTTP\/3\u2019\u00fc a\u00e7, TLS\u2019i sa\u011flam tut, kenarda sihir yap5.1 HTTP\/3\u2019\u00fc Cloudflare panelinden etkinle\u015ftirmek5.2 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1463,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-1462","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/1462","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=1462"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/1462\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/1463"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=1462"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=1462"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=1462"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}