我试图设置反向代理与wordpress和排除路径夫妇.我排除规则的工作管理,包括,..等,但它不工作/wp-json/.我怀疑这是因为. htaccess.我需要wordpress返回其余的API数据,因为我用gatsbyjs.
我花了一整天的时间试图弄清楚这一点。由于某种原因,我的setup /wp-json/返回404,它被代理到我网站前端部分的netlify服务器。如果我删除所有的代理规则,wp-json工作。
.htaccess包含默认的wordpress内容。
下面是我的虚拟主机的pastebin:https://pastebin.com/vFh6hCkN
<IfModule mod_ssl.c>
<VirtualHost *:443>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
Protocols h2 http/1.1
ServerName www.michaelharwinlaw.com
ServerAlias michaelharwinlaw.com
ServerAdmin webmaster@cyberserge.com
DocumentRoot /var/www/html/
<Directory /var/www/html>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
</Directory>
SSLProxyEngine on
ProxyPass /wp-admin/ !
ProxyPass /wp-login/ !
ProxyPass /wp-json/ !
ProxyPass /wp-content/plugins/ !
ProxyPass /wp-includes/ !
ProxyPassMatch .*\.xml !
ProxyPass / https://stag.michaelharwinlaw.com/
ProxyPassReverse / https://stag.michaelharwinlaw.com/
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/mc-error.log
CustomLog ${APACHE_LOG_DIR}/mc-access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
Include /var/www/html/wp-content/uploads/wpseo-redirects/.redirects
SSLCertificateFile /etc/letsencrypt/live/www.michaelharwinlaw.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/www.michaelharwinlaw.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
.htaccess网站
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
2条答案
按热度按时间vojdkbi01#
因为
/wp-json
不是真实的的文件或目录,在不阅读.htaccess
的情况下,本地请求将得到404
not found
响应,因此Apache将继续将请求转发到远程服务器。要修复此URL重写,我们需要将请求发送到本地
index.php
。将
ProxyPass /wp-json/ !
替换为/wp-json
不带结束斜杠/
需要处理domain/wp-json
或domain/wp-json/
的请求。任何其他不存在的URL将由远程服务器处理。
8iwquhpp2#
在文档中,请参见分页导航不起作用部分:
“这是由于WordPress生成的.htaccess文件中的一个小故障。要修复它,请删除.htaccess文件的内容,然后重新创建它。
1.在控制面板中,转到管理〉文件(编辑文件的更多信息);
1.单击指向.htaccess文件的链接以编辑其内容;
1.复制文件的内容并将其粘贴到文本编辑器中的文本文件中。这是一个预防措施,以防您的.htaccess文件有重定向,拒绝或其他方便的htaccess技巧的手动条目;
1.删除.htaccess文件中的所有内容,然后单击“更新文件”按钮;
1.在控制面板中,转到选项〉固定链接;
1.单击“更新永久链接结构”按钮为永久链接重新生成新的重写规则;
1.使用先前断开的链接测试结果;
1.将任何手动htaccess条目添加回文件中(将手动htaccess条目放在#开始WordPress之前或# END WordPress行之后。