如何修复访问WordPress时出现的HTTP 400 Bad Request错误

huangapple
go评论109阅读模式
英文:

How to fix HTTP 400 Bad Request error when accessing WordPress

问题

在WordPress站点上，我使用在Google Compute Engine上托管的Apache服务器。我遇到的问题是，当我尝试使用HTTP连接到站点时，出现400 Bad Request错误。HTTPS没有问题，而且我有SSL证书。当Certbot询问我时，我确保将HTTP重定向到HTTPS。

我还在以下文件中进行了必要的更改，但没有进行重定向。如果你有任何线索，我全听着。感谢你的帮助。

这是我的apache2.conf文件：

  1. # 这是主要的Apache服务器配置文件。它包含了
  2. # 给服务器提供指令的配置指令。
  3. # 有关详细信息，请参见http://httpd.apache.org/docs/2.4/
  4. # 以及Debian特定提示的/usr/share/doc/apache2/README.Debian。
  5. #
  6. # ...
  7. #（以下略）
  9. # 全局配置
  10. #

这是我的wordpress-https.conf文件，位于/etc/apache2/sites-enabled：

  1. <VirtualHost *:443>
  2.   ServerAdmin admin@example.com
  3.   DocumentRoot /var/www/html
  4.   SSLEngine on
  6.   <Directory /var/www/html>
  7.     Options -Indexes
  8.     AllowOverride FileInfo
  9.   </Directory>
  10.   ServerName enerdf.fr
  11.   Include /etc/letsencrypt/options-ssl-apache.conf
  12.   ServerAlias www.enerdf.fr
  13.   SSLCertificateFile /etc/letsencrypt/live/enerdf.fr/fullchain.pem
  14.   SSLCertificateKeyFile /etc/letsencrypt/live/enerdf.fr/privkey.pem
  15. </VirtualHost>
  17. <VirtualHost *:80>
  18.   ServerAdmin admin@example.com
  19.   DocumentRoot /var/www/html
  21.   <Directory /var/www/html>
  22.     Options -Indexes
  23.     AllowOverride FileInfo
  24.   </Directory>
  26.   RewriteEngine On
  27.   RewriteCond %{HTTPS} off
  28.   RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  30.   RewriteCond %{SERVER_NAME} =enerdf.fr [OR]
  31.   RewriteCond %{SERVER_NAME} =www.enerdf.fr
  32.   RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
  33. </VirtualHost>

我考虑在每次修改后重新启动服务器，但没有改变任何东西。

英文:

I am on a WordPress site hosted on Google Compute Engine with an Apache server. The problem I am facing is that when I try to connect to my site using HTTP, I get a 400 Bad Request error. There is no problem with HTTPS, and I have an SSL certificate. When Certbot asked me to, I made sure to redirect HTTP to HTTPS.

I have also made the necessary changes in the files below, but no redirection is done.If you have any leads, I am all ears. Thanks for your help.

here my apache2.conf in etc/apache2/

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-html -->

  1. # This is the main Apache server configuration file.  It contains the
  2. # configuration directives that give the server its instructions.
  3. # See http://httpd.apache.org/docs/2.4/ for detailed information about
  4. # the directives and /usr/share/doc/apache2/README.Debian about Debian specific
  5. # hints.
  6. #
  7. #
  8. # Summary of how the Apache 2 configuration works in Debian:
  9. # The Apache 2 web server configuration in Debian is quite different to
  10. # upstream&#39;s suggested way to configure the web server. This is because Debian&#39;s
  11. # default Apache2 installation attempts to make adding and removing modules,
  12. # virtual hosts, and extra configuration directives as flexible as possible, in
  13. # order to make automating the changes and administering the server as easy as
  14. # possible.
  16. # It is split into several files forming the configuration hierarchy outlined
  17. # below, all located in the /etc/apache2/ directory:
  18. #
  19. #       /etc/apache2/
  20. #       |-- apache2.conf
  21. #       |       `--  ports.conf
  22. #       |-- mods-enabled
  23. #       |       |-- *.load
  24. #       |       `-- *.conf
  25. #       |-- conf-enabled
  26. #       |       `-- *.conf
  27. #       |       `-- sites-enabled
  28. #       |       `-- *.conf
  29. #
  30. #
  31. # * apache2.conf is the main configuration file (this file). It puts the pieces
  32. #   together by including all remaining configuration files when starting up the
  33. #   web server.
  34. #
  35. # * ports.conf is always included from the main configuration file. It is
  36. #   supposed to determine listening ports for incoming connections which can be
  37. #   customized anytime.
  38. #
  39. # * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
  40. #   directories contain particular configuration snippets which manage modules,
  41. #   global configuration fragments, or virtual host configurations,
  42. #   respectively.
  43. #
  44. #   They are activated by symlinking available configuration files from their
  45. #   respective *-available/ counterparts. These should be managed by using our
  46. #   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
  47. #   their respective man pages for detailed information.
  48. #
  49. # * The binary is called apache2. Due to the use of environment variables, in
  50. #   the default configuration, apache2 needs to be started/stopped with
  51. #   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
  52. #   work with the default configuration.
  55. # Global configuration
  56. #

<!-- end snippet -->

here my conf enabled "wordpress-https.conf" in /etc/apache2/sites-enabled

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-html -->

  1. &lt;VirtualHost *:443&gt;
  2.   ServerAdmin admin@example.com
  3.   DocumentRoot /var/www/html
  4.   SSLEngine on
  6.   &lt;Directory /var/www/html&gt;
  7.     Options -Indexes
  8.     AllowOverride FileInfo
  9.   &lt;/Directory&gt;
  10.     ServerName enerdf.fr
  11. Include /etc/letsencrypt/options-ssl-apache.conf
  12. ServerAlias www.enerdf.fr
  13. SSLCertificateFile /etc/letsencrypt/live/enerdf.fr/fullchain.pem
  14. SSLCertificateKeyFile /etc/letsencrypt/live/enerdf.fr/privkey.pem
  15. &lt;/VirtualHost&gt;
  17. &lt;VirtualHost *:80&gt;
  18.   ServerAdmin admin@example.com
  19.   DocumentRoot /var/www/html
  21.   &lt;Directory /var/www/html&gt;
  22.     Options -Indexes
  23.     AllowOverride FileInfo
  24.   &lt;/Directory&gt;
  26.   RewriteEngine On
  27.   RewriteCond %{HTTPS} off
  28.   RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  30. RewriteCond %{SERVER_NAME} =enerdf.fr [OR]
  31. RewriteCond %{SERVER_NAME} =www.enerdf.fr
  32. RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
  33. &lt;/VirtualHost&gt;

<!-- end snippet -->

I thought about restarting the server after each modification, but it doesn't change anything

答案1

得分: 1

我最终发现我需要像这样在端口80上禁用SSL：

  1. <!-- 开始代码片段：js 隐藏：false 控制台：true Babel：false -->
  3. <!-- 语言：lang-html -->
  4. <VirtualHost *:80>
  5.   ServerName exemple.com
  6.   SSLEngine off
  7.   Redirect permanent / https://exemple.com
  8. </VirtualHost>
  10. <!-- 结束代码片段 -->
英文:

I finally found that I needed to disable ssl on port 80 like this :

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-html -->

  1. &lt;VirtualHost *:80&gt;
  2.   ServerName exemple.com
  3.   SSLEngine off
  4.   Redirect permanent / https://exemple.com
  5. &lt;/VirtualHost&gt;

<!-- end snippet -->

huangapple
  • 本文由 发表于 2023年3月3日 20:53:18
  • 转载请务必保留本文链接：https://go.coder-hub.com/75627333.html
  • apache
  • google-compute-engine
  • wordpress
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定