{"id":38264,"date":"2026-01-27T09:40:55","date_gmt":"2026-01-27T06:40:55","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=38264"},"modified":"2026-01-27T09:40:55","modified_gmt":"2026-01-27T06:40:55","slug":"apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/","title":{"rendered":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi"},"content":{"rendered":"

<\/p>\n

Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi<\/h2>\n

Giri\u015f<\/h2>\n

\u0130nternet d\u00fcnyas\u0131nda web sitelerinin kullan\u0131c\u0131 deneyimi, arama motoru optimizasyonu (SEO) ve genel performans\u0131 i\u00e7in URL’lerin yap\u0131s\u0131 kritik bir \u00f6neme sahiptir. Karma\u015f\u0131k, parametrelerle dolu URL’ler hem kullan\u0131c\u0131lar taraf\u0131ndan hat\u0131rlanmas\u0131 zor hem de arama motorlar\u0131 taraf\u0131ndan daha az tercih edilen bir yap\u0131 sunar. \u0130\u015fte tam bu noktada “URL yeniden yazma” (URL rewriting) devreye girer. Bu teknik, sunucu taraf\u0131nda gelen istek URL’lerini alarak, daha okunabilir, anlaml\u0131 ve SEO dostu bir formata d\u00f6n\u00fc\u015ft\u00fcrmeyi sa\u011flar.<\/p>\n

Bu makalede, Apache web sunucusunun en g\u00fc\u00e7l\u00fc mod\u00fcllerinden biri olan mod_rewrite<\/code>‘\u0131 kullanarak Ubuntu 16.04 i\u015fletim sistemi \u00fczerinde URL’leri nas\u0131l yeniden yazaca\u011f\u0131m\u0131z\u0131 detayl\u0131 bir \u015fekilde inceleyece\u011fiz. Ubuntu 16.04, uzun s\u00fcreli destek (LTS) s\u00fcr\u00fcm\u00fc olmas\u0131 nedeniyle bir\u00e7ok sunucu ortam\u0131nda hala yayg\u0131n olarak kullan\u0131lmaktad\u0131r ve Apache 2.4 s\u00fcr\u00fcm\u00fc ile birlikte gelir. mod_rewrite<\/code>‘\u0131n temellerinden ba\u015flayarak, kurulumunu, yap\u0131land\u0131rmas\u0131n\u0131, yayg\u0131n kullan\u0131m senaryolar\u0131n\u0131 ve hata ay\u0131klama y\u00f6ntemlerini ad\u0131m ad\u0131m ele alaca\u011f\u0131z. Amac\u0131m\u0131z, web geli\u015ftiricilerine ve sistem y\u00f6neticilerine, temiz URL’ler olu\u015fturma, y\u00f6nlendirmeler yapma ve web uygulamalar\u0131n\u0131 daha esnek hale getirme konusunda kapsaml\u0131 bir rehber sunmakt\u0131r.<\/p>\n

mod_rewrite Nedir?<\/h2>\n

mod_rewrite<\/code>, Apache HTTP Sunucusu i\u00e7in g\u00fc\u00e7l\u00fc ve esnek bir URL manip\u00fclasyon mod\u00fcl\u00fcd\u00fcr. Gelen URL isteklerini, d\u00fczenli ifadeler (regular expressions) kullanarak dinamik olarak yeniden yazma veya ba\u015fka bir URL’ye y\u00f6nlendirme yetene\u011fi sunar. Bu mod\u00fcl, web sunucusunun \u00e7ekirdek i\u015flevselli\u011fine entegre edilmi\u015f olup, HTTP isteklerinin i\u015flenme d\u00f6ng\u00fcs\u00fcn\u00fcn erken a\u015famalar\u0131nda devreye girer. Bu sayede, taray\u0131c\u0131ya g\u00f6sterilen URL ile sunucunun dahili olarak i\u015fledi\u011fi URL aras\u0131nda bir soyutlama katman\u0131 olu\u015fturulur.<\/p>\n

mod_rewrite<\/code>‘\u0131n g\u00fcc\u00fc, karma\u015f\u0131k ko\u015fullar tan\u0131mlayabilme ve bu ko\u015fullara ba\u011fl\u0131 olarak farkl\u0131 yeniden yazma veya y\u00f6nlendirme eylemleri ger\u00e7ekle\u015ftirebilmesinden gelir. \u00d6rne\u011fin, bir web sitesindeki urun.php?id=123<\/code> gibi bir URL’yi kullan\u0131c\u0131 dostu urun\/123<\/code> \u015feklinde g\u00f6sterebilirsiniz. Ya da HTTP \u00fczerinden gelen t\u00fcm istekleri otomatik olarak HTTPS’ye y\u00f6nlendirebilirsiniz. Bu esneklik, modern web uygulamalar\u0131n\u0131n geli\u015ftirilmesinde, SEO stratejilerinde ve g\u00fcvenlik \u00f6nlemlerinde mod_rewrite<\/code>‘\u0131 vazge\u00e7ilmez bir ara\u00e7 haline getirir.<\/p>\n

Kurallar genellikle iki ana yerde tan\u0131mlanabilir:
\n1. Sunucu Yap\u0131land\u0131rma Dosyalar\u0131:<\/strong> httpd.conf<\/code>, apache2.conf<\/code> veya sites-enabled<\/code> dizinindeki sanal host yap\u0131land\u0131rma dosyalar\u0131 (.conf<\/code>). Bu y\u00f6ntem, performans\u0131 art\u0131r\u0131r \u00e7\u00fcnk\u00fc Apache sunucu ba\u015flat\u0131ld\u0131\u011f\u0131nda veya yeniden y\u00fcklendi\u011finde kurallar\u0131 bir kez okur ve \u00f6nbelle\u011fe al\u0131r.
\n2. .htaccess<\/code> Dosyalar\u0131:<\/strong> Belirli dizinlerde bulunan da\u011f\u0131t\u0131lm\u0131\u015f yap\u0131land\u0131rma dosyalar\u0131d\u0131r. Bu dosyalar, sunucu y\u00f6neticisinin ana yap\u0131land\u0131rma dosyalar\u0131na eri\u015fimi olmayan kullan\u0131c\u0131lar\u0131n (\u00f6rne\u011fin payla\u015f\u0131ml\u0131 hosting kullan\u0131c\u0131lar\u0131) kendi dizinleri i\u00e7in \u00f6zel kurallar tan\u0131mlamas\u0131na olanak tan\u0131r. Ancak, her gelen istekte Apache’nin ilgili dizin ve \u00fcst dizinlerde .htaccess<\/code> dosyalar\u0131n\u0131 aramas\u0131 ve okumas\u0131 gerekti\u011fi i\u00e7in performans\u0131 olumsuz etkileyebilir. G\u00fcvenlik ve performans a\u00e7\u0131s\u0131ndan m\u00fcmk\u00fcnse sunucu yap\u0131land\u0131rma dosyalar\u0131 tercih edilmelidir.<\/p>\n

Ubuntu 16.04 \u00fczerinde Apache 2.4 ile \u00e7al\u0131\u015f\u0131rken, genellikle \/etc\/apache2\/apache2.conf<\/code> ana yap\u0131land\u0131rma dosyas\u0131 veya \/etc\/apache2\/sites-available\/<\/code> i\u00e7indeki sanal host dosyalar\u0131 (.conf<\/code> uzant\u0131l\u0131) kullan\u0131l\u0131r. E\u011fer .htaccess<\/code> kullanmak isterseniz, ilgili dizin i\u00e7in AllowOverride All<\/code> y\u00f6nergesini ayarlaman\u0131z gerekecektir.<\/p>\n

Ortam Kurulumu ve \u00d6n Gereksinimler<\/h2>\n

mod_rewrite<\/code>‘\u0131 kullanmaya ba\u015flamadan \u00f6nce, Ubuntu 16.04 sunucunuzda Apache’nin kurulu ve mod_rewrite<\/code> mod\u00fcl\u00fcn\u00fcn etkinle\u015ftirilmi\u015f oldu\u011fundan emin olmal\u0131y\u0131z. Ayr\u0131ca, .htaccess<\/code> dosyalar\u0131 kullanmay\u0131 planl\u0131yorsan\u0131z, Apache’nin bu dosyalardaki kurallar\u0131 okumas\u0131na izin vermemiz gerekecektir.<\/p>\n

Ubuntu 16.04’te Apache Kurulumu<\/h3>\n

E\u011fer sunucunuzda Apache hen\u00fcz kurulu de\u011filse, a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 izleyerek kurabilirsiniz:<\/p>\n

1. Paket listelerini g\u00fcncelleyin:<\/p>\n

sudo apt update<\/code><\/pre>\n
2.  Apache web sunucusunu kurun:<\/p>\n
sudo apt install apache2<\/code><\/pre>\n
3.  Kurulumdan sonra Apache servisinin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n:<\/p>\n
sudo systemctl status apache2<\/code><\/pre>\n
    \u00c7\u0131kt\u0131da active (running)<\/code> ifadesini g\u00f6rmelisiniz.
\n4.  G\u00fcvenlik duvar\u0131 (UFW) kullan\u0131yorsan\u0131z, Apache’ye gelen trafi\u011fe izin vermeniz gerekir:<\/p>\n
sudo ufw allow 'Apache Full'\n    sudo ufw enable<\/code><\/pre>\n
    Taray\u0131c\u0131n\u0131zda sunucunuzun IP adresini ziyaret etti\u011finizde “Apache2 Ubuntu Default Page” sayfas\u0131n\u0131 g\u00f6rmelisiniz.<\/p>\n
mod_rewrite Mod\u00fcl\u00fcn\u00fc Etkinle\u015ftirme<\/h3>\n
Apache kurulumu tamamland\u0131ktan sonra, mod_rewrite<\/code> mod\u00fcl\u00fcn\u00fc etkinle\u015ftirmemiz gerekir. Ubuntu\/Debian tabanl\u0131 sistemlerde bu i\u015flem a2enmod<\/code> (Apache 2 Enable Mod) komutu ile kolayca yap\u0131l\u0131r:<\/p>\n
1.  mod_rewrite<\/code> mod\u00fcl\u00fcn\u00fc etkinle\u015ftirin:<\/p>\n
sudo a2enmod rewrite<\/code><\/pre>\n
    Bu komut, \/etc\/apache2\/mods-available\/rewrite.load<\/code> dosyas\u0131ndan sembolik bir ba\u011flant\u0131 olu\u015fturarak mod\u00fcl\u00fc etkinle\u015ftirir.
\n2.  De\u011fi\u015fikliklerin etkili olmas\u0131 i\u00e7in Apache servisini yeniden ba\u015flat\u0131n:<\/p>\n
sudo systemctl restart apache2<\/code><\/pre>\n
Art\u0131k mod_rewrite<\/code> kullan\u0131ma haz\u0131rd\u0131r.<\/p>\n
Dizin \u0130zinlerini Yap\u0131land\u0131rma (AllowOverride)<\/h3>\n
E\u011fer URL yeniden yazma kurallar\u0131n\u0131z\u0131 .htaccess<\/code> dosyalar\u0131nda tan\u0131mlamak istiyorsan\u0131z (ki bu, \u00f6zellikle payla\u015f\u0131ml\u0131 hosting ortamlar\u0131nda yayg\u0131nd\u0131r), Apache’nin ilgili dizinler i\u00e7in .htaccess<\/code> dosyalar\u0131n\u0131 okumas\u0131na izin vermeniz gerekir. Bu izin, Apache’nin ana yap\u0131land\u0131rma dosyas\u0131 olan \/etc\/apache2\/apache2.conf<\/code> i\u00e7inde veya sanal host yap\u0131land\u0131rma dosyalar\u0131n\u0131zda (\/etc\/apache2\/sites-available\/*.conf<\/code>) Directory<\/code> blo\u011fu i\u00e7inde AllowOverride<\/code> y\u00f6nergesi ile verilir.<\/p>\n
Varsay\u0131lan olarak, Apache’nin k\u00f6k dizini olan \/var\/www\/html<\/code> i\u00e7in AllowOverride None<\/code> ayar\u0131 mevcuttur. Bu, .htaccess<\/code> dosyalar\u0131n\u0131n bu dizinde ve alt dizinlerinde dikkate al\u0131nmayaca\u011f\u0131 anlam\u0131na gelir. Bu ayar\u0131 AllowOverride All<\/code> olarak de\u011fi\u015ftirmemiz gerekir:<\/p>\n
1.  Apache ana yap\u0131land\u0131rma dosyas\u0131n\u0131 bir metin d\u00fczenleyici ile a\u00e7\u0131n:<\/p>\n
sudo nano \/etc\/apache2\/apache2.conf<\/code><\/pre>\n
2.  Dosya i\u00e7inde <\/code> blo\u011funu bulun. \u0130\u00e7indeki AllowOverride None<\/code> sat\u0131r\u0131n\u0131 AllowOverride All<\/code> olarak de\u011fi\u015ftirin:<\/p>\n
\n            Options Indexes FollowSymLinks\n            AllowOverride All   # Buray\u0131 None'dan All olarak de\u011fi\u015ftirin\n            Require all granted\n    <\/Directory><\/code><\/pre>\n
    E\u011fer web siteniz \/var\/www\/html<\/code> d\u0131\u015f\u0131nda ba\u015fka bir dizinde ise, o dizin i\u00e7in de benzer bir Directory<\/code> blo\u011fu olu\u015fturman\u0131z veya mevcut blo\u011fu d\u00fczenlemeniz gerekebilir. \u00d6rne\u011fin:<\/p>\n
\n            Options Indexes FollowSymLinks\n            AllowOverride All\n            Require all granted\n    <\/Directory><\/code><\/pre>\n
3.  De\u011fi\u015fiklikleri kaydedip kapat\u0131n (Nano’da Ctrl+O<\/code>, Enter<\/code>, Ctrl+X<\/code>).
\n4.  Apache yap\u0131land\u0131rmas\u0131nda s\u00f6zdizimi hatas\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol edin:<\/p>\n
sudo apache2ctl configtest<\/code><\/pre>\n
    Syntax OK<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 almal\u0131s\u0131n\u0131z.
\n5.  Apache servisini yeniden ba\u015flat\u0131n:<\/p>\n
sudo systemctl restart apache2<\/code><\/pre>\n
Art\u0131k \/var\/www\/html<\/code> dizininde (veya ayarlad\u0131\u011f\u0131n\u0131z ba\u015fka bir dizinde) .htaccess<\/code> dosyalar\u0131 olu\u015fturabilir ve mod_rewrite<\/code> kurallar\u0131n\u0131z\u0131 buraya yazabilirsiniz.<\/p>\n
mod_rewrite Temel Kurallar\u0131 ve S\u00f6zdizimi<\/h2>\n
mod_rewrite<\/code> kurallar\u0131 genellikle \u00fc\u00e7 ana y\u00f6nergeden olu\u015fur: RewriteEngine<\/code>, RewriteCond<\/code> ve RewriteRule<\/code>. Bu y\u00f6nergeler, karma\u015f\u0131k URL yeniden yazma mant\u0131klar\u0131 olu\u015fturmak i\u00e7in bir araya getirilir.<\/p>\n
RewriteEngine<\/h3>\n
Bu y\u00f6nerge, mod_rewrite<\/code> motorunu a\u00e7\u0131p kapatmak i\u00e7in kullan\u0131l\u0131r. Kurallar\u0131n\u0131z\u0131n \u00e7al\u0131\u015fmas\u0131 i\u00e7in mutlaka On<\/code> olarak ayarlanmal\u0131d\u0131r.<\/p>\n
S\u00f6zdizimi:<\/strong><\/p>\n
RewriteEngine On\n
veya<\/h2>\nRewriteEngine Off<\/code><\/pre>\n
Genellikle .htaccess<\/code> dosyas\u0131n\u0131n veya sanal host yap\u0131land\u0131rma blo\u011funun en ba\u015f\u0131na yerle\u015ftirilir.<\/p>\n
RewriteCond<\/h3>\n
RewriteCond<\/code> (Rewrite Condition – Yeniden Yazma Ko\u015fulu), bir RewriteRule<\/code>‘\u0131n uygulanabilmesi i\u00e7in kar\u015f\u0131lanmas\u0131 gereken ko\u015fullar\u0131 tan\u0131mlar. Bir RewriteRule<\/code>‘dan \u00f6nce birden fazla RewriteCond<\/code> y\u00f6nergesi tan\u0131mlanabilir. T\u00fcm ko\u015fullar varsay\u0131lan olarak AND<\/code> mant\u0131\u011f\u0131yla birle\u015ftirilir, ancak [OR]<\/code> bayra\u011f\u0131 ile bu davran\u0131\u015f de\u011fi\u015ftirilebilir.<\/p>\n
S\u00f6zdizimi:<\/strong><\/p>\n
RewriteCond TestString CondPattern [Flags]<\/code><\/pre>\n
*   TestString<\/code>:<\/strong> Kontrol edilecek dize. Bu genellikle sunucu de\u011fi\u015fkenleri (%{REQUEST_FILENAME}<\/code>, %{HTTP_HOST}<\/code>, %{HTTPS}<\/code>, %{QUERY_STRING}<\/code> vb.) veya geriye d\u00f6n\u00fck referanslar (%1<\/code>, %2<\/code> vb.) i\u00e7erir.
\n*   CondPattern<\/code>:<\/strong> TestString<\/code> ile e\u015fle\u015fecek d\u00fczenli ifade (regex) deseni.
\n*   [Flags]<\/code>:<\/strong> Ko\u015fulun davran\u0131\u015f\u0131n\u0131 de\u011fi\u015ftiren iste\u011fe ba\u011fl\u0131 bayraklar.<\/p>\n
Yayg\u0131n RewriteCond<\/code> Bayraklar\u0131:<\/strong>
\n*   [NC]<\/code> (No Case):<\/strong> Desen e\u015fle\u015fmesini b\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harf duyars\u0131z yapar.
\n*   [OR]<\/code> (Or):<\/strong> Bu ko\u015fulu bir sonraki RewriteCond<\/code> ile OR<\/code> mant\u0131\u011f\u0131yla birle\u015ftirir. Aksi takdirde varsay\u0131lan AND<\/code> kullan\u0131l\u0131r.
\n*   [L]<\/code> (Last):<\/strong> Bu kural e\u015fle\u015firse, ba\u015fka hi\u00e7bir kural\u0131n i\u015flenmemesini sa\u011flar.<\/p>\n
\u00d6rnekler:<\/strong>
\n*   Host ad\u0131n\u0131n www.example.com<\/code> olup olmad\u0131\u011f\u0131n\u0131 kontrol etme:<\/p>\n
RewriteCond %{HTTP_HOST} ^www\\.example\\.com$ [NC]<\/code><\/pre>\n
*   \u0130stenen dosyan\u0131n var olup olmad\u0131\u011f\u0131n\u0131 kontrol etme:<\/p>\n
RewriteCond %{REQUEST_FILENAME} !-f<\/code><\/pre>\n
    (!-f<\/code> “dosya de\u011filse” anlam\u0131na gelir. -f<\/code> “dosya ise”, -d<\/code> “dizin ise” anlam\u0131na gelir.)
\n*   HTTPS \u00fczerinden gelip gelmedi\u011fini kontrol etme:<\/p>\n
RewriteCond %{HTTPS} off<\/code><\/pre>\n
RewriteRule<\/h3>\n
RewriteRule<\/code> (Yeniden Yazma Kural\u0131), as\u0131l yeniden yazma veya y\u00f6nlendirme i\u015flemini ger\u00e7ekle\u015ftiren y\u00f6nergedir. Bir veya daha fazla RewriteCond<\/code> taraf\u0131ndan belirlenen ko\u015fullar kar\u015f\u0131land\u0131\u011f\u0131nda tetiklenir.<\/p>\n
S\u00f6zdizimi:<\/strong><\/p>\n
RewriteRule Pattern Substitution [Flags]<\/code><\/pre>\n
*   Pattern<\/code>:<\/strong> Gelen URL yolunun (domain ve query string hari\u00e7) e\u015fle\u015ftirilece\u011fi d\u00fczenli ifade deseni. Bu desen, RewriteCond<\/code>‘daki CondPattern<\/code>‘dan farkl\u0131 olarak, URL’nin kendisini hedefler.
\n*   Substitution<\/code>:<\/strong> Pattern<\/code> ile e\u015fle\u015fen URL’nin yerine ge\u00e7ecek yeni URL. Bu bir dosya yolu, tam bir URL veya bir sunucu de\u011fi\u015fkeni olabilir. Yakalanan gruplar ($1<\/code>, $2<\/code> vb.) burada kullan\u0131labilir.
\n*   [Flags]<\/code>:<\/strong> Kural\u0131n davran\u0131\u015f\u0131n\u0131 de\u011fi\u015ftiren iste\u011fe ba\u011fl\u0131 bayraklar.<\/p>\n
Yayg\u0131n RewriteRule<\/code> Bayraklar\u0131:<\/strong>
\n*   [L]<\/code> (Last):<\/strong> Bu kural e\u015fle\u015firse, Apache’nin di\u011fer t\u00fcm RewriteRule<\/code>‘lar\u0131 i\u015flemeyi durdurmas\u0131n\u0131 sa\u011flar. Bu, genellikle bir kural\u0131n nihai hedef oldu\u011fu durumlarda kullan\u0131l\u0131r.
\n*   [R]<\/code> veya [R=301]<\/code> (Redirect):<\/strong> Taray\u0131c\u0131ya bir HTTP y\u00f6nlendirmesi (varsay\u0131lan olarak 302 Temporary Redirect) g\u00f6nderir. [R=301]<\/code> kal\u0131c\u0131 bir y\u00f6nlendirme (Permanent Redirect) i\u00e7in kullan\u0131l\u0131r ve SEO a\u00e7\u0131s\u0131ndan \u00f6nemlidir.
\n*   [NC]<\/code> (No Case):<\/strong> Desen e\u015fle\u015fmesini b\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harf duyars\u0131z yapar.
\n*   [QSA]<\/code> (Query String Append):<\/strong> Orijinal iste\u011fin sorgu dizesini (query string) yeniden yaz\u0131lan URL’ye ekler. Bu bayrak \u00e7ok s\u0131k kullan\u0131l\u0131r, \u00e7\u00fcnk\u00fc aksi takdirde sorgu dizeleri genellikle kaybolur.
\n*   [P]<\/code> (Proxy):<\/strong> Yeniden yaz\u0131lan URL’yi dahili olarak bir proxy iste\u011fi olarak i\u015fler. mod_proxy<\/code> mod\u00fcl\u00fcn\u00fcn etkinle\u015ftirilmi\u015f olmas\u0131n\u0131 gerektirir.
\n*   [F]<\/code> (Forbidden):<\/strong> E\u015fle\u015fen URL’ye eri\u015fimi engeller ve 403 Forbidden hatas\u0131 d\u00f6nd\u00fcr\u00fcr.
\n*   [E=VAR:VALUE]<\/code> (Environment Variable):<\/strong> Belirli bir ortam de\u011fi\u015fkenini ayarlar.<\/p>\n
Regex Temelleri<\/h3>\n
mod_rewrite<\/code>‘\u0131 etkin bir \u015fekilde kullanmak i\u00e7in temel d\u00fczenli ifade (regex) bilgisine sahip olmak \u00f6nemlidir. \u0130\u015fte baz\u0131 temel regex karakterleri:
\n*   .<\/code> (Nokta):<\/strong> Herhangi bir karakterle e\u015fle\u015fir (sat\u0131r sonu hari\u00e7).
\n   <\/em><\/code> (Y\u0131ld\u0131z):<\/strong> \u00d6nceki karakterin s\u0131f\u0131r veya daha fazla tekrar\u0131yla e\u015fle\u015fir.
\n*   +<\/code> (Art\u0131):<\/strong> \u00d6nceki karakterin bir veya daha fazla tekrar\u0131yla e\u015fle\u015fir.
\n*   ?<\/code> (Soru \u0130\u015fareti):<\/strong> \u00d6nceki karakterin s\u0131f\u0131r veya bir tekrar\u0131yla e\u015fle\u015fir.
\n*   ^<\/code> (\u015eapka):<\/strong> Dizinin ba\u015flang\u0131c\u0131yla e\u015fle\u015fir.
\n*   $<\/code> (Dolar):<\/strong> Dizinin sonuyla e\u015fle\u015fir.
\n*   []<\/code> (K\u00f6\u015feli Parantez):<\/strong> K\u00f6\u015feli parantez i\u00e7indeki herhangi bir karakterle e\u015fle\u015fir (\u00f6rne\u011fin, [a-z]<\/code> k\u00fc\u00e7\u00fck harflerle, [0-9]<\/code> rakamlarla e\u015fle\u015fir).
\n*   ()<\/code> (Parantez):<\/strong> Bir grubu yakalar. Yakalanan gruplara RewriteRule<\/code> i\u00e7inde $1<\/code>, $2<\/code> vb. ile eri\u015filir. RewriteCond<\/code> i\u00e7inde ise %1<\/code>, %2<\/code> vb. ile eri\u015filir.
\n*   |<\/code> (Dikey \u00c7izgi):<\/strong> OR<\/code> operat\u00f6r\u00fc (\u00f6rne\u011fin, (elma|armut)<\/code>).
\n*   \\<\/code> (Ters E\u011fik \u00c7izgi):<\/strong> \u00d6zel karakterleri ka\u00e7\u0131\u015f karakteri olarak kullan\u0131r (\u00f6rne\u011fin, \\.<\/code> ger\u00e7ek bir nokta karakteriyle e\u015fle\u015fir, \\s<\/code> bo\u015fluk karakteriyle e\u015fle\u015fir).<\/p>\n
Yayg\u0131n Kullan\u0131m Senaryolar\u0131 ve \u00d6rnekler<\/h2>\n
\u015eimdi mod_rewrite<\/code>‘\u0131n g\u00fcc\u00fcn\u00fc g\u00f6steren baz\u0131 pratik \u00f6rneklere g\u00f6z atal\u0131m. Bu \u00f6rnekler genellikle .htaccess<\/code> dosyas\u0131na yaz\u0131l\u0131r, ancak ayn\u0131 kurallar sanal host yap\u0131land\u0131rmas\u0131na da entegre edilebilir.<\/p>\n
“Pretty URLs” Olu\u015fturma (Anlaml\u0131 URL’ler)<\/h3>\n
Bu, mod_rewrite<\/code>‘\u0131n en yayg\u0131n kullan\u0131m alanlar\u0131ndan biridir. Dinamik i\u00e7eri\u011fe sahip sayfalar\u0131n URL’lerini daha okunabilir ve SEO dostu hale getiririz.<\/p>\n
\u00d6rnek 1: \u00dcr\u00fcn ID’sini URL’ye Ta\u015f\u0131ma<\/strong>
\nexample.com\/urun.php?id=123<\/code> yerine example.com\/urun\/123<\/code> kullanmak.<\/p>\n
# .htaccess dosyas\u0131na\nRewriteEngine On\nRewriteRule ^urun\/([0-9]+)\/?$ urun.php?id=$1 [NC,L,QSA]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   ^urun\/<\/code>: URL’nin urun\/<\/code> ile ba\u015flad\u0131\u011f\u0131n\u0131 belirtir.
\n*   ([0-9]+)<\/code>: Bir veya daha fazla rakamdan olu\u015fan bir grubu yakalar. Bu yakalanan de\u011fer urun.php<\/code>‘ye $1<\/code> olarak aktar\u0131l\u0131r.
\n*   \/?<\/code>: \u0130ste\u011fe ba\u011fl\u0131 olarak sondaki e\u011fik \u00e7izgiyi e\u015fle\u015ftirir.
\n*   urun.php?id=$1<\/code>: Yeniden yaz\u0131lan dahili URL.
\n*   [NC,L,QSA]<\/code>: B\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harf duyars\u0131z e\u015fle\u015fme (NC<\/code>), bu kural e\u015fle\u015fti\u011finde di\u011fer kurallar\u0131 durdur (L<\/code>), orijinal sorgu dizesini ekle (QSA<\/code>).<\/p>\n
\u00d6rnek 2: Kategori Ad\u0131n\u0131 URL’ye Ta\u015f\u0131ma<\/strong>
\nexample.com\/kategori.php?ad=elektronik<\/code> yerine example.com\/kategori\/elektronik<\/code> kullanmak.<\/p>\n
RewriteEngine On\nRewriteRule ^kategori\/([a-zA-Z0-9_-]+)\/?$ kategori.php?ad=$1 [NC,L,QSA]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   ([a-zA-Z0-9_-]+)<\/code>: Harflerden, rakamlardan, alt \u00e7izgiden veya tireden olu\u015fan bir veya daha fazla karakter grubunu yakalar.<\/p>\n
www Olmayan Adresleri www’ye Y\u00f6nlendirme (veya Tersini)<\/h3>\n
Web sitenizin tek bir kanonik URL’ye sahip olmas\u0131 SEO i\u00e7in \u00f6nemlidir. Genellikle example.com<\/code> adresini www.example.com<\/code> adresine y\u00f6nlendirmek tercih edilir.<\/p>\n
# www olmayan adresleri www'ye y\u00f6nlendirme\nRewriteEngine On\nRewriteCond %{HTTP_HOST} ^example\\.com [NC]\nRewriteRule ^(.*)$ http:\/\/www.example.com\/$1 [L,R=301,NC]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   RewriteCond %{HTTP_HOST} ^example\\.com [NC]<\/code>: Gelen iste\u011fin host ad\u0131n\u0131n example.com<\/code> (veya b\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harf duyars\u0131z olarak example.com<\/code>) olup olmad\u0131\u011f\u0131n\u0131 kontrol eder.
\n   RewriteRule ^(.<\/em>)$ http:\/\/www.example.com\/$1 [L,R=301,NC]<\/code>: E\u011fer ko\u015ful do\u011fruysa, t\u00fcm URL yolunu yakalar ((.*)<\/code>) ve http:\/\/www.example.com\/<\/code> adresine 301 kal\u0131c\u0131 y\u00f6nlendirme ile $1<\/code> olarak ekler.<\/p>\n
Tersini yapmak isterseniz (www.example.com<\/code> adresini example.com<\/code> adresine y\u00f6nlendirme):<\/p>\n
# www olan adresleri www olmayana y\u00f6nlendirme\nRewriteEngine On\nRewriteCond %{HTTP_HOST} ^www\\.example\\.com [NC]\nRewriteRule ^(.*)$ http:\/\/example.com\/$1 [L,R=301,NC]<\/code><\/pre>\n
HTTP’den HTTPS’ye Y\u00f6nlendirme<\/h3>\n
SSL\/TLS sertifikas\u0131 kurulu olan siteler i\u00e7in t\u00fcm trafi\u011fi g\u00fcvenli HTTPS protokol\u00fcne y\u00f6nlendirmek hem g\u00fcvenlik hem de SEO a\u00e7\u0131s\u0131ndan \u00e7ok \u00f6nemlidir.<\/p>\n
# HTTP'den HTTPS'ye y\u00f6nlendirme\nRewriteEngine On\nRewriteCond %{HTTPS} off\nRewriteRule ^(.*)$ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NC]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   RewriteCond %{HTTPS} off<\/code>: \u0130stek HTTPS \u00fczerinden gelmiyorsa (yani HTTP ise) ko\u015ful do\u011fru olur.
\n   RewriteRule ^(.<\/em>)$ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NC]<\/code>: T\u00fcm URL yolunu yakalar ve ayn\u0131 host ve URI ile HTTPS’ye 301 kal\u0131c\u0131 y\u00f6nlendirme yapar.<\/p>\n
Dosya Uzant\u0131lar\u0131n\u0131 Gizleme<\/h3>\n
page.php<\/code> gibi URL’leri page<\/code> olarak g\u00f6stermek, URL’leri daha temiz hale getirir.<\/p>\n
# .php uzant\u0131s\u0131n\u0131 gizleme\nRewriteEngine On\nRewriteCond %{REQUEST_FILENAME} !-f\nRewriteCond %{REQUEST_FILENAME} !-d\nRewriteRule ^([^\\.]+)$ $1.php [NC,L]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   RewriteCond %{REQUEST_FILENAME} !-f<\/code>: \u0130stenen URI’nin fiziksel bir dosya olmad\u0131\u011f\u0131n\u0131 kontrol eder.
\n*   RewriteCond %{REQUEST_FILENAME} !-d<\/code>: \u0130stenen URI’nin fiziksel bir dizin olmad\u0131\u011f\u0131n\u0131 kontrol eder. Bu iki ko\u015ful, ger\u00e7ek dosya veya dizin adlar\u0131n\u0131n yeniden yaz\u0131lmas\u0131n\u0131 engeller.
\n*   RewriteRule ^([^\\.]+)$ $1.php [NC,L]<\/code>: Nokta i\u00e7ermeyen herhangi bir URL yolunu yakalar ([^\\.]+<\/code>) ve sonuna .php<\/code> ekleyerek dahili olarak yeniden yazar.<\/p>\n
Belirli Dosyalar\u0131 veya Dizinleri Engelleme<\/h3>\n
Hassas dosyalara veya dizinlere do\u011frudan eri\u015fimi engellemek i\u00e7in mod_rewrite<\/code> kullan\u0131labilir.<\/p>\n
\u00d6rnek 1: .htaccess<\/code> Dosyas\u0131na Eri\u015fimi Engelleme<\/strong>
\nBu, genellikle varsay\u0131lan olarak zaten engellenmi\u015ftir, ancak ekstra g\u00fcvenlik i\u00e7in eklenebilir.<\/p>\n
# .htaccess dosyas\u0131na do\u011frudan eri\u015fimi engelleme\nRewriteEngine On\nRewriteRule ^\\.htaccess$ - [F]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   RewriteRule ^\\.htaccess$ - [F]<\/code>: URL’si .htaccess<\/code> olan herhangi bir iste\u011fi 403 Forbidden hatas\u0131yla engeller. -<\/code> hedef URL olmad\u0131\u011f\u0131 anlam\u0131na gelir, \u00e7\u00fcnk\u00fc sadece engellemek istiyoruz.<\/p>\n
\u00d6rnek 2: Belirli Bir Dizin \u0130\u00e7eri\u011fine Eri\u015fimi Engelleme<\/strong>
\n\u00d6rne\u011fin, \/private<\/code> dizinine web \u00fczerinden eri\u015fimi engellemek.<\/p>\n
# \/private dizinine eri\u015fimi engelleme\nRewriteEngine On\nRewriteRule ^private\/.*$ - [F]<\/code><\/pre>\n
Dizinlere Eri\u015fim Kontrol\u00fc (Front Controller Deseni)<\/h3>\n
Modern web \u00e7er\u00e7evelerinin \u00e7o\u011fu (Laravel, Symfony, CodeIgniter vb.) bir “front controller” deseni kullan\u0131r. Bu desende, t\u00fcm istekler tek bir ana PHP dosyas\u0131na (genellikle index.php<\/code>) y\u00f6nlendirilir ve bu dosya iste\u011fi uygun denetleyiciye ve eyleme y\u00f6nlendirir.<\/p>\n
# Front Controller deseni i\u00e7in\nRewriteEngine On\nRewriteCond %{REQUEST_FILENAME} !-f\nRewriteCond %{REQUEST_FILENAME} !-d\nRewriteRule ^(.*)$ index.php\/$1 [L]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   Bu kurallar, fiziksel olarak var olan bir dosya (-f<\/code>) veya dizin (-d<\/code>) istenmedi\u011fi s\u00fcrece, gelen t\u00fcm istekleri index.php<\/code> dosyas\u0131na y\u00f6nlendirir. $1<\/code> yakalanan URL yolunu index.php<\/code>‘ye parametre olarak iletir. Baz\u0131 \u00e7er\u00e7eveler index.php?url=$1<\/code> \u015feklinde sorgu dizesi kullanabilir.<\/p>\n
Eski URL’leri Yeni URL’lere Y\u00f6nlendirme (301 Kal\u0131c\u0131 Y\u00f6nlendirme)<\/h3>\n
Bir web sitesinin yap\u0131s\u0131 de\u011fi\u015fti\u011finde veya sayfalar ta\u015f\u0131nd\u0131\u011f\u0131nda, eski URL’lerden yeni URL’lere 301 kal\u0131c\u0131 y\u00f6nlendirmeler yapmak SEO i\u00e7in hayati \u00f6neme sahiptir. Bu, arama motorlar\u0131n\u0131n eski sayfan\u0131n de\u011ferini yeni sayfaya aktarmas\u0131n\u0131 sa\u011flar.<\/p>\n
# Eski URL'den yeni URL'ye 301 y\u00f6nlendirme\nRewriteEngine On\nRewriteRule ^eski-sayfa\\.html$ \/yeni-sayfa.html [L,R=301]\nRewriteRule ^eski-dizin\/(.*)$ \/yeni-dizin\/$1 [L,R=301]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   \u0130lk kural, eski-sayfa.html<\/code> adresine gelen bir iste\u011fi yeni-sayfa.html<\/code> adresine kal\u0131c\u0131 olarak y\u00f6nlendirir.
\n*   \u0130kinci kural, eski-dizin<\/code> alt\u0131ndaki t\u00fcm URL’leri yeni-dizin<\/code> alt\u0131na kal\u0131c\u0131 olarak y\u00f6nlendirir, URL yolunun geri kalan\u0131n\u0131 korur.<\/p>\n
IP Adresine G\u00f6re Eri\u015fim Engelleme<\/h3>\n
Belirli IP adreslerinden gelen eri\u015fimi engellemek i\u00e7in mod_rewrite<\/code> kullan\u0131labilir.<\/p>\n
# Belirli bir IP adresinden gelen eri\u015fimi engelleme\nRewriteEngine On\nRewriteCond %{REMOTE_ADDR} ^192\\.168\\.1\\.100$\nRewriteRule ^.*$ - [F]<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   RewriteCond %{REMOTE_ADDR} ^192\\.168\\.1\\.100$<\/code>: \u0130ste\u011fin geldi\u011fi IP adresinin 192.168.1.100 olup olmad\u0131\u011f\u0131n\u0131 kontrol eder.
\n   RewriteRule ^.<\/em>$ - [F]<\/code>: E\u011fer IP e\u015fle\u015firse, t\u00fcm istekleri 403 Forbidden hatas\u0131yla engeller.<\/p>\n
mod_rewrite Hata Ay\u0131klama (Debugging)<\/h2>\n
mod_rewrite<\/code> kurallar\u0131 karma\u015f\u0131k olabilir ve beklenen \u015fekilde \u00e7al\u0131\u015fmayabilir. Bu durumda, hata ay\u0131klama yetenekleri b\u00fcy\u00fck \u00f6nem ta\u015f\u0131r. Apache 2.4 ve sonraki s\u00fcr\u00fcmlerde (Ubuntu 16.04'te kullan\u0131lan s\u00fcr\u00fcm<\/code>), RewriteLog<\/code> ve RewriteLogLevel<\/code> y\u00f6nergeleri kald\u0131r\u0131lm\u0131\u015ft\u0131r. Bunun yerine, Apache’nin genel LogLevel<\/code> y\u00f6nergesi kullan\u0131l\u0131r.<\/p>\n
LogLevel debug rewrite:trace8<\/h3>\n
mod_rewrite<\/code> ile ilgili ayr\u0131nt\u0131l\u0131 g\u00fcnl\u00fck kayd\u0131 almak i\u00e7in, sanal host yap\u0131land\u0131rma dosyan\u0131za veya \/etc\/apache2\/apache2.conf<\/code> dosyas\u0131na a\u015fa\u011f\u0131daki sat\u0131r\u0131 ekleyebilirsiniz:<\/p>\n
LogLevel debug rewrite:trace8<\/code><\/pre>\n
A\u00e7\u0131klama:<\/strong>
\n*   LogLevel debug<\/code>: Genel hata ay\u0131klama d\u00fczeyini debug<\/code> olarak ayarlar.
\n*   rewrite:trace8<\/code>: mod_rewrite<\/code> mod\u00fcl\u00fc i\u00e7in \u00f6zel olarak trace8<\/code> seviyesinde (en y\u00fcksek detay seviyesi) g\u00fcnl\u00fck kayd\u0131 tutulmas\u0131n\u0131 sa\u011flar.<\/p>\n
Bu ayar\u0131 ekledikten sonra Apache’yi yeniden ba\u015flatman\u0131z gerekir:<\/p>\n
sudo systemctl restart apache2<\/code><\/pre>\n
Hata g\u00fcnl\u00fcklerini (\/var\/log\/apache2\/error.log<\/code>) izleyerek mod_rewrite<\/code> kurallar\u0131n\u0131n nas\u0131l i\u015flendi\u011fini g\u00f6rebilirsiniz:<\/p>\n
sudo tail -f \/var\/log\/apache2\/error.log<\/code><\/pre>\n
Bu g\u00fcnl\u00fckler, hangi kurallar\u0131n uyguland\u0131\u011f\u0131n\u0131, hangi ko\u015fullar\u0131n e\u015fle\u015fti\u011fini veya e\u015fle\u015fmedi\u011fini ve URL’nin nas\u0131l yeniden yaz\u0131ld\u0131\u011f\u0131n\u0131 ad\u0131m ad\u0131m g\u00f6sterir. Bu bilgiler, kurallar\u0131n\u0131zdaki hatalar\u0131 tespit etmek i\u00e7in paha bi\u00e7ilmezdir.<\/p>\n
apache2ctl configtest<\/h3>\n
mod_rewrite<\/code> kurallar\u0131n\u0131z\u0131 veya Apache yap\u0131land\u0131rman\u0131z\u0131 de\u011fi\u015ftirdikten sonra, Apache’yi yeniden ba\u015flatmadan \u00f6nce s\u00f6zdizimi hatalar\u0131n\u0131 kontrol etmek her zaman iyi bir uygulamad\u0131r:<\/p>\n
sudo apache2ctl configtest<\/code><\/pre>\n
E\u011fer Syntax OK<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 al\u0131rsan\u0131z, yap\u0131land\u0131rman\u0131zda bir s\u00f6zdizimi hatas\u0131 yoktur. Aksi takdirde, hata mesaj\u0131 size sorunun nerede oldu\u011funu g\u00f6sterecektir.<\/p>\n
Performans ve G\u00fcvenlik Hususlar\u0131<\/h2>\n
mod_rewrite<\/code> g\u00fc\u00e7l\u00fc bir ara\u00e7 olsa da, yanl\u0131\u015f kullan\u0131m\u0131 performans\u0131 d\u00fc\u015f\u00fcrebilir veya g\u00fcvenlik a\u00e7\u0131klar\u0131 olu\u015fturabilir.<\/p>\n
.htaccess vs. Sunucu Konfig\u00fcrasyonu<\/h3>\n
Daha \u00f6nce de belirtildi\u011fi gibi, .htaccess<\/code> dosyalar\u0131 her gelen istekte Apache taraf\u0131ndan aran\u0131r ve okunur. Bu, \u00f6zellikle y\u00fcksek trafikli sitelerde \u00f6nemli bir performans d\u00fc\u015f\u00fc\u015f\u00fcne neden olabilir. M\u00fcmk\u00fcnse, mod_rewrite<\/code> kurallar\u0131n\u0131z\u0131 sunucu yap\u0131land\u0131rma dosyalar\u0131n\u0131za (\/etc\/apache2\/sites-available\/*.conf<\/code> i\u00e7indeki sanal host yap\u0131land\u0131rmalar\u0131) yerle\u015ftirmeniz \u00f6nerilir. Bu, Apache’nin kurallar\u0131 yaln\u0131zca bir kez y\u00fcklemesini ve \u00f6nbelle\u011fe almas\u0131n\u0131 sa\u011flar, b\u00f6ylece her istekte dosya okuma y\u00fck\u00fcnden ka\u00e7\u0131n\u0131l\u0131r.<\/p>\n
E\u011fer .htaccess<\/code> kullanmak zorundaysan\u0131z (\u00f6rne\u011fin payla\u015f\u0131ml\u0131 hosting ortam\u0131nda), kurallar\u0131 m\u00fcmk\u00fcn oldu\u011funca basit tutmaya \u00e7al\u0131\u015f\u0131n ve \u00e7ok fazla RewriteCond<\/code> veya karma\u015f\u0131k regex desenlerinden ka\u00e7\u0131n\u0131n.<\/p>\n
Karma\u015f\u0131k Regex Kullan\u0131m\u0131n\u0131n Etkisi<\/h3>\n
D\u00fczenli ifadeler g\u00fc\u00e7l\u00fcd\u00fcr, ancak ayn\u0131 zamanda i\u015flemci yo\u011fun olabilir. \u00c7ok karma\u015f\u0131k veya verimsiz yaz\u0131lm\u0131\u015f regex desenleri, her istekte Apache’nin daha fazla CPU d\u00f6ng\u00fcs\u00fc harcamas\u0131na neden olabilir. Kurallar\u0131n\u0131z\u0131 yazarken m\u00fcmk\u00fcn oldu\u011funca basit ve optimize edilmi\u015f regex desenleri kullanmaya \u00f6zen g\u00f6sterin. Testler yaparak performans \u00fczerindeki etkilerini g\u00f6zlemleyin.<\/p>\n
G\u00fcvenlik Riskleri<\/h3>\n
Yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f mod_rewrite<\/code> kurallar\u0131, sitenizde g\u00fcvenlik a\u00e7\u0131klar\u0131na yol a\u00e7abilir. \u00d6rne\u011fin:
\n*   A\u00e7\u0131k Y\u00f6nlendirmeler:<\/strong> Kullan\u0131c\u0131 girdisini do\u011frudan bir RewriteRule<\/code>‘da hedef URL olarak kullanmak, sald\u0131rganlar\u0131n sitenizi kullanarak kullan\u0131c\u0131lar\u0131 k\u00f6t\u00fc ama\u00e7l\u0131 sitelere y\u00f6nlendirmesine izin verebilir. Her zaman kullan\u0131c\u0131 girdisini dikkatlice do\u011frulay\u0131n ve filtreleyin.
\n*   Bilgi S\u0131z\u0131nt\u0131s\u0131:<\/strong> Yanl\u0131\u015fl\u0131kla hassas dosyalar\u0131n veya dizinlerin do\u011frudan eri\u015fime a\u00e7\u0131lmas\u0131.
\n*   DoS Sald\u0131r\u0131lar\u0131:<\/strong> Sonsuz y\u00f6nlendirme d\u00f6ng\u00fcleri veya \u00e7ok karma\u015f\u0131k regex’ler, sunucunuzu DoS (Denial of Service) sald\u0131r\u0131lar\u0131na kar\u015f\u0131 savunmas\u0131z hale getirebilir. [L]<\/code> (Last) bayra\u011f\u0131n\u0131 do\u011fru yerlerde kullanarak sonsuz d\u00f6ng\u00fcleri \u00f6nleyin.<\/p>\n
Herhangi bir mod_rewrite<\/code> kural\u0131 uygulamadan \u00f6nce, etkilerini dikkatlice test etmek ve g\u00fcvenlik a\u00e7\u0131s\u0131ndan g\u00f6zden ge\u00e7irmek kritik \u00f6neme sahiptir.<\/p>\n
Sonu\u00e7<\/h2>\n
Apache’nin mod_rewrite<\/code> mod\u00fcl\u00fc, web geli\u015ftiricilerine ve sistem y\u00f6neticilerine URL’leri manip\u00fcle etme konusunda inan\u0131lmaz bir g\u00fc\u00e7 ve esneklik sunar. Ubuntu 16.04 \u00fczerinde Apache 2.4 ile \u00e7al\u0131\u015f\u0131rken, bu mod\u00fcl\u00fc kullanarak temiz ve anlaml\u0131 URL’ler olu\u015fturabilir, SEO’yu iyile\u015ftirebilir, kullan\u0131c\u0131 deneyimini zenginle\u015ftirebilir ve web uygulamalar\u0131n\u0131z\u0131n altyap\u0131s\u0131n\u0131 daha esnek hale getirebilirsiniz.<\/p>\n
Bu makalede, mod_rewrite<\/code>‘\u0131n temel prensiplerini, Ubuntu 16.04 ortam\u0131nda nas\u0131l kurulup etkinle\u015ftirilece\u011fini, RewriteEngine<\/code>, RewriteCond<\/code> ve RewriteRule<\/code> gibi ana y\u00f6nergelerin s\u00f6zdizimini ve yayg\u0131n kullan\u0131m senaryolar\u0131n\u0131 detayl\u0131 \u00f6rneklerle ele ald\u0131k. Ayr\u0131ca, hata ay\u0131klama teknikleri ve performans ile g\u00fcvenlik hususlar\u0131 hakk\u0131nda \u00f6nemli bilgiler payla\u015ft\u0131k.<\/p>\n
Unutmay\u0131n ki mod_rewrite<\/code>‘\u0131n g\u00fcc\u00fc, ayn\u0131 zamanda karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 da beraberinde getirir. Kurallar\u0131n\u0131z\u0131 yazarken dikkatli olun, d\u00fczenli ifadeleri do\u011fru kullan\u0131n ve her zaman de\u011fi\u015fiklikleri test edin. M\u00fcmk\u00fcn oldu\u011funca sunucu yap\u0131land\u0131rma dosyalar\u0131n\u0131 tercih ederek performans\u0131 art\u0131r\u0131n ve gereksiz .htaccess<\/code> kullan\u0131m\u0131ndan ka\u00e7\u0131n\u0131n. Bu rehber, mod_rewrite<\/code> d\u00fcnyas\u0131na ad\u0131m atman\u0131z i\u00e7in sa\u011flam bir temel olu\u015fturacakt\u0131r. Uygulamal\u0131 deneyim kazand\u0131k\u00e7a, bu g\u00fc\u00e7l\u00fc mod\u00fcl\u00fcn t\u00fcm potansiyelini ke\u015ffedebileceksiniz.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi\nGiri\u015f\n\u0130nternet d\u00fcnyas\u0131nda web sitelerinin kullan\u0131c\u0131 deneyimi, arama","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1468],"tags":[],"class_list":{"0":"post-38264","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-ubuntu","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nApache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi\" \/>\n<meta property=\"og:description\" content=\"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi Giri\u015f \u0130nternet d\u00fcnyas\u0131nda web sitelerinin kullan\u0131c\u0131 deneyimi, arama\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-01-27T06:40:55+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"19 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi\",\"datePublished\":\"2026-01-27T06:40:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/\"},\"wordCount\":3170,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Ubuntu\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/\",\"name\":\"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-01-27T06:40:55+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/","og_locale":"tr_TR","og_type":"article","og_title":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi","og_description":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi Giri\u015f \u0130nternet d\u00fcnyas\u0131nda web sitelerinin kullan\u0131c\u0131 deneyimi, arama","og_url":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-01-27T06:40:55+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"19 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi","datePublished":"2026-01-27T06:40:55+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/"},"wordCount":3170,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Ubuntu"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/","url":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/","name":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-01-27T06:40:55+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/apache-ve-ubuntu-16-04-uzerinde-mod_rewrite-ile-url-yeniden-yazma-rehberi\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Apache ve Ubuntu 16.04 \u00dczerinde mod_rewrite ile URL Yeniden Yazma Rehberi"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=38264"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38264\/revisions"}],"predecessor-version":[{"id":38265,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38264\/revisions\/38265"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=38264"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=38264"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=38264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}