# HG changeset patch # User Andrey Alexeev # Date 1322066525 0 # Node ID 8796246b31e14a9adb74bc8382e3698874e59a2f # Parent ec4626d04879970d1059b6e5bbb1f6f7b63aa1ca - Added new entries to faq.xml - Deleted denied shite diff -r ec4626d04879 -r 8796246b31e1 xml/en/docs/faq.xml --- a/xml/en/docs/faq.xml Wed Nov 23 16:31:50 2011 +0000 +++ b/xml/en/docs/faq.xml Wed Nov 23 16:42:05 2011 +0000 @@ -15,6 +15,26 @@ + + + + + + + + + + + + + + + + + + + + diff -r ec4626d04879 -r 8796246b31e1 xml/en/docs/faq_trailing_slash_redirect.xml --- a/xml/en/docs/faq_trailing_slash_redirect.xml Wed Nov 23 16:31:50 2011 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,57 +0,0 @@ - - -
- -
- - -Q: -What is the right way to do a trailing slash redirect for the -requests without a trailing slash in the URI? - - - -A: -If the URI refers to a static file or a directory then nginx -will do the redirect automatically. If it's not a static -content and REQUEST_URI should be proxied to the backends, -the following configuration will work: - - - - -location ~* /[^/\.]+$ { - rewrite ^(.*)$ http://$http_host$1/ permanent; -} - - - - -However, a better way of doing that would be separating -static content and proxying: - - - - -location / { -    index index.php; -    try_files $uri $uri/ /index.php?$args; -} - -location ~ (?^.*/[^/.]+$) { -    return 301 http://$host$url/$is_args$args; -} - -location ~ \.php$ { - ... -} - - - -
- -
\ No newline at end of file