проблемы при создании перенаправлений 301 в Apache 2.4.3x с использованием htaccess - PullRequest
Новая
       16

проблемы при создании перенаправлений 301 в Apache 2.4.3x с использованием htaccess

0 голосов
/ 08 ноября 2018

Я недавно обновил свой веб-сайт с протокола http до https.

Я добавил следующий код в мой файл .htaccess, чтобы перенаправить весь трафик http на https на моем веб-сайте. 

RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

Теперь, когда я ищу статьи на своем веб-сайте с помощью Google (которые ранее были проиндексированы Google, когда сайт использовал протокол HTTP.) И нажимаю на результаты поиска, он перенаправляется на https://www.example.com.

Например:

если я нажму на http://www.example.com/my-article-1 (или наберу его в строке браузера), он будет перенаправлен на https://www.example.com.

Я бы хотел перенаправить все эти http ссылки на https

Например:

если я нажму на http://www.example.com/my-article-1, оно должно перейти к https://www.example.com/my-article-1

Я пытался создать 301 редирект в файле .htaccess 

redirect  /my-article-1 https://www.example.com/my-article-1

Я не работал. Приведенный выше код был добавлен прямо под первым кодом в этом вопросе

Как создать правильное перенаправление 301 для всех моих веб-страниц?

Я использую хостинг Linux с Apache 2.4.33 и CMS Drupal 7, на которой работает сайт.

В моем Drupal CMS

включена поддержка чистых URL *1040*

Я узнал о статье в Drupal org о размещении чистых URL и попробовал следующие комбинации 

# Various rewrite rules.

<IfModule mod_rewrite.c>

   RewriteEngine on



 # Added by Me 


 RewriteBase /

 #RewriteRule  ^/(.*)$ https://www.domain.in/serial-programming-tutorials  [R=301,L]

 #Above statement redirects to https://www.domain.in/



 #RewriteRule  ^serial-programming-tutorials$ https://www.domain.in/serial-programming-tutorials  [R=301,L]

 #Above statement gives "The page isn’t redirecting properly" Error in Browser



 #RewriteRule  ^/serial-programming-tutorials$ https://www.domain.in/serial-programming-tutorials  [R=301,L]

 #Above statement redirects to https://www.domain.in/

Ниже мой файл .htaccess. 

#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes.
<FilesMatch "\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl)(~|\.sw[op]|\.bak|\.orig|\.save)?$|^(\.(?!well-known).*|Entries.*|Repository|Root|Tag|Template|composer\.(json|lock))$|^#.*#$|\.php(~|\.sw[op]|\.bak|\.orig\.save)$">
  <IfModule mod_authz_core.c>
    Require all denied
  </IfModule>
  <IfModule !mod_authz_core.c>
    Order allow,deny
  </IfModule>
</FilesMatch>

# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php

# Set the default handler.
DirectoryIndex index.php index.html index.htm

# Override PHP settings that cannot be changed at runtime. See
# sites/default/default.settings.php and drupal_environment_initialize() in
# includes/bootstrap.inc for settings that can be changed at runtime.

# PHP 5, Apache 1 and 2.
<IfModule mod_php5.c>
  php_flag magic_quotes_gpc                 off
  php_flag magic_quotes_sybase              off
  php_flag register_globals                 off
  php_flag session.auto_start               off
  php_value mbstring.http_input             pass
  php_value mbstring.http_output            pass
  php_flag mbstring.encoding_translation    off
</IfModule>

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
  # Enable expirations.
  ExpiresActive On

  # Cache all files for 2 weeks after access (A).
  ExpiresDefault A1209600

  <FilesMatch \.php$>
    # Do not allow PHP scripts to be cached unless they explicitly send cache
    # headers themselves. Otherwise all scripts would have to overwrite the
    # headers set by mod_expires if they want another caching behavior. This may
    # fail if an error occurs early in the bootstrap process, and it may cause
    # problems if a non-Drupal PHP file is installed in a subdirectory.
    ExpiresActive Off
  </FilesMatch>
</IfModule>



# Various rewrite rules.
<IfModule mod_rewrite.c>
  RewriteEngine on

  # Added by Me 

  RewriteBase /
  #RewriteRule  ^/(.*)$ https://www.domain.in/serial-programming-tutorials  [R=301,L]
  #Above statement redirects to https://www.xanthium.in/

  #RewriteRule  ^serial-programming-tutorials$ https://www.domain.in/serial-programming-tutorials  [R=301,L]
  #Above statement gives "The page isn’t redirecting properly" Error in Browser

  #RewriteRule  ^/serial-programming-tutorials$ https://www.domain.in/serial-programming-tutorials  [R=301,L]
  #Above statement redirects to https://www.domain.in/

  # Set "protossl" to "s" if we were accessed via https://.  This is used later
  # if you enable "www." stripping or enforcement, in order to ensure that
  # you don't bounce between http and https.
  RewriteRule ^ - [E=protossl]
  RewriteCond %{HTTPS} on
  RewriteRule ^ - [E=protossl:s]

  # Make sure Authorization HTTP header is available to PHP
  # even when running as CGI or FastCGI.
  RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

  # Block access to "hidden" directories whose names begin with a period. This
  # includes directories used by version control systems such as Subversion or
  # Git to store control files. Files whose names begin with a period, as well
  # as the control files used by CVS, are protected by the FilesMatch directive
  # above.
  #
  # NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is
  # not possible to block access to entire directories from .htaccess, because
  # <DirectoryMatch> is not allowed here.
  #
  # If you do not have mod_rewrite installed, you should remove these
  # directories from your webroot or otherwise protect them from being
  # downloaded.
  RewriteRule "/\.|^\.(?!well-known/)" - [F]

  # If your site can be accessed both with and without the 'www.' prefix, you
  # can use one of the following settings to redirect users to your preferred
  # URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
  #
  # To redirect all users to access the site WITH the 'www.' prefix,
  # (http://example.com/... will be redirected to http://www.example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} .
  # RewriteCond %{HTTP_HOST} !^www\. [NC]
  # RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  #
  # To redirect all users to access the site WITHOUT the 'www.' prefix,
  # (http://www.example.com/... will be redirected to http://example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
  # RewriteRule ^ http%{ENV:protossl}://%1%{REQUEST_URI} [L,R=301]

  # Modify the RewriteBase if you are using Drupal in a subdirectory or in a
  # VirtualDocumentRoot and the rewrite rules are not working properly.
  # For example if your site is at http://example.com/drupal uncomment and
  # modify the following line:
  # RewriteBase /drupal
  #
  # If your site is running in a VirtualDocumentRoot at http://example.com/,
  # uncomment the following line:
  # RewriteBase /



  # Pass all requests not referring directly to files in the filesystem to
  # index.php. Clean URLs are handled in drupal_environment_initialize().
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !=/favicon.ico
  RewriteRule ^ index.php [L]

  # Rules to correctly serve gzip compressed CSS and JS files.
  # Requires both mod_rewrite and mod_headers to be enabled.
  <IfModule mod_headers.c>
    # Serve gzip compressed CSS files if they exist and the client accepts gzip.
    RewriteCond %{HTTP:Accept-encoding} gzip
    RewriteCond %{REQUEST_FILENAME}\.gz -s
    RewriteRule ^(.*)\.css $1\.css\.gz [QSA]

    # Serve gzip compressed JS files if they exist and the client accepts gzip.
    RewriteCond %{HTTP:Accept-encoding} gzip
    RewriteCond %{REQUEST_FILENAME}\.gz -s
    RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

    # Serve correct content types, and prevent mod_deflate double gzip.
    RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1]
    RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1]

    <FilesMatch "(\.js\.gz|\.css\.gz)$">
      # Serve correct encoding type.
      Header set Content-Encoding gzip
      # Force proxies to cache gzipped & non-gzipped css/js files separately.
      Header append Vary Accept-Encoding
    </FilesMatch>
  </IfModule>
</IfModule>

# Add headers to all responses.
<IfModule mod_headers.c>
  # Disable content sniffing, since it's an attack vector.
  Header always set X-Content-Type-Options nosniff
</IfModule>

RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.domain.in/$1 [R=301,L]

Ответы [ 2 ]

0 голосов
/ 15 ноября 2018

Порядок размещения утверждений важен для функционирования файла .htaccess, на что указывает @ MrWhite.

Я изменил свой файл htaccess, как показано ниже, для решения проблемы. 

# Various rewrite rules.
<IfModule mod_rewrite.c>
  RewriteEngine on

  #------------------------------------------------------------------#
  # Added by to redirect all http to https
  # Placing it here solved my problem
  #------------------------------------------------------------------#
      RewriteEngine On
      RewriteCond %{SERVER_PORT} 80
      RewriteRule ^(.*)$ https://www.domain.in/$1 [R=301,L]
  #-------------------------------------------------------------------#


  # Set "protossl" to "s" if we were accessed via https://.  This is used later
  # if you enable "www." stripping or enforcement, in order to ensure that
  # you don't bounce between http and https.
  RewriteRule ^ - [E=protossl]
  RewriteCond %{HTTPS} on
  RewriteRule ^ - [E=protossl:s]



 # If your site can be accessed both with and without the 'www.' prefix, you
  # can use one of the following settings to redirect users to your preferred
  # URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
  #
  # To redirect all users to access the site WITH the 'www.' prefix,
  # (http://example.com/... will be redirected to http://www.example.com/...)
  # uncomment the following:
    RewriteCond %{HTTP_HOST} .
    RewriteCond %{HTTP_HOST} !^www\. [NC]
    RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Размещение приведенного ниже оператора чуть ниже IfModule mod_rewrite.c (в файле .htaccess), как показано, решило все мои проблемы 

<IfModule mod_rewrite.c>
      RewriteEngine on

      #------------------------------------------------------------------#
      # Added by to redirect all http to https
      # Placing it here solved my problem
      #------------------------------------------------------------------#
          RewriteEngine On
          RewriteCond %{SERVER_PORT} 80
          RewriteRule ^(.*)$ https://www.domain.in/$1 [R=301,L]
      #-------------------------------------------------------------------#

Сейчас

http://www.domain.in перенаправляет на https://www.domain.in и

http://www.domain.in/tutorial-1 перенаправляет на https://www.domain.in/tutorial-1

0 голосов
/ 12 ноября 2018

Вы поместили перенаправление HTTP на HTTPS не в том месте. Он должен идти вверху вашего .htaccess файла, а не в конце.

Поместив его в конец, «фронт-контроллер» Drupal уже переписал запрос на index.php. Более поздний редирект HTTP-HTTPS затем преобразует это во внешнее перенаправление (в следующем цикле обработки) и по существу перенаправляет все в корень документа.

Порядок директив (mod_rewrite) в .htaccess важен.

...