使用.htaccess mod_rewrite重定向到移动版网站

时间:2013-10-25 19:00:41

标签: php .htaccess symfony mod-rewrite

我正在使用Symfony 2来开发一个Web应用程序。我想将移动用户从移动浏览器访问http://m.mysite.comhttp://www.mysite.com时将其重定向到http://mysite.com

我下载了MobileDetectBundle来检测和管理重定向。我跟着他们usage example,但我在第4步遇到了问题,他们说:

  

配置您的http服务器。确保在您的http服务器虚拟主机中使http://m.site.com使用app_mobile.php作为其脚本文件而不是app.php。

由于我在共享服务器(hostgator)上运行,我认为我可以编辑.htaccess文件(位于mySymfonyAppDir / web /中)来执行此操作。

我想出了下面的.htaccess,但它有问题。这是正确的方法(使用htaccess),还是有另一种方法使http://m.mysite.com使用app_mobile.php作为其脚本文件?如果这种方法没问题,.htaccess应该是什么样的?目前的一个显然忽略了RewriteCond %{HTTP_HOST} !^m\..和/或RewriteCond %{HTTP_HOST} ^m\..行。

非常感谢。

# Use the front controller as index file. It serves as 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
# startpage (path "/") because otherwise Apache will apply the rewritting rules
# to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
DirectoryIndex app.php

<IfModule mod_rewrite.c>
    RewriteEngine On


    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.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 startpage 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 %{HTTP_HOST} ^m\..
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
    RewriteRule ^app_mobile\.php(/(.*)|$) %{CONTEXT_PREFIX}/$2 [R=301,L]

    RewriteCond %{HTTP_HOST} !^m\..
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
    RewriteRule ^app\.php(/(.*)|$) %{CONTEXT_PREFIX}/$2 [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]

    # The following rewrites all other queries to the front controller. The
    # condition ensures that if you are using Apache aliases to do mass virtual
    # hosting, the base path will be prepended to allow proper resolution of the
    # app.php file; it will work in non-aliased environments as well, providing
    # a safe, one-size fits all solution.
    RewriteCond %{HTTP_HOST} ^m\.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)(.+)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]
    RewriteRule .? %{ENV:BASE}app_mobile.php [L]

    RewriteCond %{HTTP_HOST} !^m\.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)(.+)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]
    RewriteRule .? %{ENV:BASE}app.php [L]
</IfModule>

<IfModule !mod_rewrite.c>
    <IfModule mod_alias.c>
        # When mod_rewrite is not available, we instruct a temporary redirect of
        # the startpage to the front controller explicitly so that the website
        # and the generated links can still be used.
        RedirectMatch 302 ^/$ /app.php/
        # RedirectTemp cannot be used instead
    </IfModule>
</IfModule>

0 个答案:

没有答案