Apache虚拟主机isn'；t重定向到HTTPS

我已经成功地在我的服务器上安装了Gitlab，并将其配置为在Apache上运行，因为这是我用来托管当前站点的

我使用Let's Encrypt在我的域中添加SSL加密，并选择使它们“安全”，因此在我的所有

.conf

文件中都放置了重写规则，以将HTTP请求重定向到HTTPS

这适用于除Gitlab文件之外的所有其他

.conf

文件

它使用以下命令来处理重定向：

RewriteCond %{SERVER_NAME} = gitlab.example.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]

有人能帮我指出它为什么不能正常工作吗

以下是完整虚拟主机：

<VirtualHost *:80>
  ServerName gitlab.example.com
  ServerSignature Off

  ProxyPreserveHost On

  # Ensure that encoded slashes are not decoded but left in their encoded state.
  # http://doc.gitlab.com/ce/api/projects.html#get-single-project
  AllowEncodedSlashes NoDecode

  <Location />
    # New authorization commands for apache 2.4 and up
    # http://httpd.apache.org/docs/2.4/upgrading.html#access
    Require all granted

    #Allow forwarding to gitlab-workhorse
    ProxyPassReverse http://127.0.0.1:8181
    ProxyPassReverse http://gitlab.example.com/

  </Location>

  # Apache equivalent of nginx try files
  # http://serverfault.com/questions/290784/what-is-apaches-equivalent-of-nginxs-try-files
  # http://stackoverflow.com/questions/10954516/apache2-proxypass-for-rails-app-gitlab
  RewriteEngine on

  #Don't escape encoded characters in api requests
  RewriteCond %{REQUEST_URI} ^/api/v3/.*
  RewriteRule .* http://127.0.0.1:8181%{REQUEST_URI} [P,QSA,NE]

  #Forward all requests to gitlab-workhorse except existing files like error documents
  RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f [OR]
  RewriteCond %{REQUEST_URI} ^/uploads/.*
  RewriteRule .* http://127.0.0.1:8181%{REQUEST_URI} [P,QSA]

  # needed for downloading attachments
  DocumentRoot /opt/gitlab/embedded/service/gitlab-rails/public

  #Set up apache error documents, if back end goes down (i.e. 503 error) then a maintenance/deploy page is thrown up.
  ErrorDocument 404 /404.html
  ErrorDocument 422 /422.html
  ErrorDocument 500 /500.html
  ErrorDocument 503 /deploy.html

  # It is assumed that the log directory is in /var/log/httpd.
  # For Debian distributions you might want to change this to
  # /var/log/apache2.
  LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b" common_forwarded
  ErrorLog  ${APACHE_LOG_DIR}/gitlab.example.com_error.log
  CustomLog ${APACHE_LOG_DIR}/gitlab.example.com_forwarded.log common_forwarded
  CustomLog ${APACHE_LOG_DIR}/gitlab.example.com_access.log combined env=!dontlog
  CustomLog ${APACHE_LOG_DIR}/gitlab.example.com.log combined
#    ErrorLog ${APACHE_LOG_DIR}/error.log
#    CustomLog ${APACHE_LOG_DIR}/access.log showmedomain

RewriteCond %{SERVER_NAME} = gitlab.example.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

ServerName gitlab.example.com
服务器签名关闭
代理主机
#确保编码的斜杠未被解码，而是处于编码状态。
# http://doc.gitlab.com/ce/api/projects.html#get-单个项目
AllowEncodeDSL节点代码
#针对apache 2.4及更高版本的新授权命令
# http://httpd.apache.org/docs/2.4/upgrading.html#access
要求所有授权
#允许转发到gitlab workhorse
ProxyPassReversehttp://127.0.0.1:8181
ProxyPassReversehttp://gitlab.example.com/
#相当于Apache的nginx try文件
# http://serverfault.com/questions/290784/what-is-apaches-equivalent-of-nginxs-try-files
# http://stackoverflow.com/questions/10954516/apache2-proxypass-for-rails-app-gitlab
重新启动发动机
#不转义api请求中的编码字符
重写cond%{REQUEST_URI}^/api/v3/*
重写规则。*http://127.0.0.1:8181%{REQUEST_URI}[P，QSA，NE]
#将所有请求转发到gitlab workhorse，但现有文件（如错误文档）除外
重写cond%{DOCUMENT\u ROOT}/%{REQUEST\u FILENAME}-f[或]
RewriteCond%{REQUEST_URI}^/uploads/*
重写规则。*http://127.0.0.1:8181%{REQUEST_URI}[P，QSA]
#需要下载附件
DocumentRoot/opt/gitlab/embedded/service/gitlab-rails/public
#设置apache错误文档，如果后端出现故障（即503错误），则会弹出维护/部署页面。
错误文档404/404.html
错误文档422/422.html
ErrorDocument 500/500.html
ErrorDocument 503/deploy.html
#假设日志目录位于/var/log/httpd中。
#对于Debian发行版，您可能希望将其更改为
#/var/log/apache2。
日志格式“%{X-Forwarded-For}i%l%u%t\%r\”%>s%b”公共\u转发
ErrorLog${APACHE\u LOG\u DIR}/gitlab.example.com\u error.LOG
CustomLog${APACHE\u LOG\u DIR}/gitlab.example.com\u forwarded.LOG common\u forwarded
CustomLog${APACHE\u LOG\u DIR}/gitlab.example.com\u access.LOG combined env=！唐特洛
CustomLog${APACHE\u LOG\u DIR}/gitlab.example.com.LOG合并
#ErrorLog${APACHE_LOG_DIR}/error.LOG
#CustomLog${APACHE\u LOG\u DIR}/access.LOG showmedomain
RewriteCond%{SERVER_NAME}=gitlab.example.com
重写规则^https://%{SERVER_NAME}%{REQUEST_URI}[END，QSA，R=permanent]

好吧，奇怪的是，现在可以了。。。我昨天在我的电脑上测试了这个，然后在隐姓埋名中测试，然后在我的移动网络上独立测试，但它不起作用。然而今天它确实。。。这可能是由于客户端缓存了一些东西造成的吗？好吧，奇怪的是，这现在起作用了。。。我昨天在我的电脑上测试了这个，然后在隐姓埋名中测试，然后在我的移动网络上独立测试，但它不起作用。然而今天它确实。。。这可能是由于客户端缓存了一些东西造成的吗？