3 Comments

1. Witam.
   Ja jestem masochistą i trzymam pliki SF 4 / 5 w katalogu public_html.
   W nim w pliku .htaccess umieszczam wpis:

   Options All -Indexes

   RewriteEngine On
   RewriteBase /
   RewriteCond %{HTTP_HOST} ^(.+?)\.$
   RewriteRule ^ http://%1%{REQUEST_URI} [L,R=302,NE]

   # Przekierowanie na adres bez www
   RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
   RewriteRule ^(.*)$ http://%1%{REQUEST_URI} [R=301,QSA,NC,L]

   RewriteCond %{REQUEST_FILENAME} !/public/
   RewriteRule ^(.*)$ /public/$1 [L]

   Natomiast w pliku .htaccess w obrębie katalogu public aplikacji Symfony dorzucam takie oto dyrektywy (pomijam tutaj liczne wpisy, które blokują boty, popularne ataki typu SQL Injection, XSS etc.):

   # Use the front controller as index file. It serves as a fallback solution when
   # every other rewrite/redirect fails (e.g. in an aliased environment without
   # mod_rewrite). Additionally, this reduces the matching process for the
   # start page (path „/”) because otherwise Apache will apply the rewriting rules
   # to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
   DirectoryIndex index.php

   # By default, Apache does not evaluate symbolic links if you did not enable this
   # feature in your server configuration. Uncomment the following line if you
   # install assets as symlinks or if you experience problems related to symlinks
   # when compiling LESS/Sass/CoffeScript assets.
   # Options FollowSymlinks

   # Disabling MultiViews prevents unwanted negotiation, e.g. „/index” should not resolve
   # to the front controller „/index.php” but be rewritten to „/index.php/index”.

   Options -MultiViews

   RewriteEngine On

   # Determine the RewriteBase automatically and set it as environment variable.
   # If you are using Apache aliases to do mass virtual hosting or installed the
   # project in a subdirectory, the base path will be prepended to allow proper
   # resolution of the index.php file and to redirect to the correct URI. It will
   # work in environments without path prefix as well, providing a safe, one-size
   # fits all solution. But as you do not need it in this case, you can comment
   # the following 2 lines to eliminate the overhead.
   RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
   RewriteRule ^(.*) – [E=BASE:%1]

   # Sets the HTTP_AUTHORIZATION header removed by Apache
   RewriteCond %{HTTP:Authorization} .
   RewriteRule ^ – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

   # Redirect to URI without front controller to prevent duplicate content
   # (with and without `/index.php`). Only do this redirect on the initial
   # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
   # endless redirect loop (request -> rewrite to front controller ->
   # redirect -> request -> …).
   # So in case you get a „too many redirects” error or you always get redirected
   # to the start page because your Apache does not expose the REDIRECT_STATUS
   # environment variable, you have 2 choices:
   # – disable this feature by commenting the following 2 lines or
   # – use Apache >= 2.3.9 and replace all L flags by END flags and remove the
   # following RewriteCond (best solution)
   RewriteCond %{ENV:REDIRECT_STATUS} ^$
   RewriteRule ^index\.php(?:/(.*)|$) %{ENV:BASE}/$1 [R=301,L]

   # If the requested filename exists, simply serve it.
   # We only want to let Apache serve files and not directories.
   RewriteCond %{REQUEST_FILENAME} -f
   RewriteRule ^ – [L]

   # Rewrite all other queries to the front controller.
   RewriteRule ^ %{ENV:BASE}/index.php [L]

   # When mod_rewrite is not available, we instruct a temporary redirect of
   # the start page to the front controller explicitly so that the website
   # and the generated links can still be used.
   RedirectMatch 307 ^/$ /index.php/
   # RedirectTemp cannot be used instead

   BTW, ostatnio robiłem migrację z SF 3.4 na SF 4.4 i mam problem z cachem podczas korzystania z wtyczki FOS UserBundle na MyDevil.net. Na localhoście wszystko jest ok. Czym się to objawia? Otóż loguję się na stronie, następnie dokonuję wylogowania, a widok z Twig nie odświeża się (w pliku config/packages/twig.yml mam wpis cache: false). Sesja została zamknięta, a na stronie pokazuje, że jestem zalogowany. Po odświeżeniu okna w przeglądarce (CTRL+SHIFT+R / CTRL+F5) problem znika.
   Co z tym fantem zrobić?

   Odpowiedz

2. Cześć!
   Dzięki za artykuł – pomógł 🙂

   Odpowiedz

3. Konkretnie. Wskazówki, które nie jednemu się mogą przydać 🙂

   Odpowiedz