2
Because, since the redirect is unconditional, you end up redirecting again after the URL has been rewritten to index.php (the WordPress front-controller).
When you request /somepage.php:
You are redirected to /somepage (by the first rule). The redirect response is sent back to the client.
On the second request, /somepage is internally rewritten to /index....
1
Since siteA.com and siteB.com point to different vHosts/servers then you can remove all the existing directives in siteB.com/.htaccess and use the simpler mod_alias Redirect and RedirectMatch directives.
For example:
# siteB.com/.htaccess
# Specific redirects
Redirect 301 /foo https://siteA.com/another-foo
Redirect 301 /bar https://siteA.com/another-bar
...
1
Your nginx is trying to connect to localhost inside the container. You have to either use host networking for the container or you need to link the nginx container to the WordPress container.
In the docker-compose file that would be:
external_links:
- wordpress:wordpress
Then you can use
proxy_pass http://wordpress/
in your nginx config. You don't need ...
Only top voted, non community-wiki answers of a minimum length are eligible
Related Tags
wordpress × 1730nginx × 521
apache-2.2 × 269
php × 211
mysql × 138
.htaccess × 121
apache-2.4 × 118
php-fpm × 109
linux × 101
ubuntu × 94
centos × 71
redirect × 61
amazon-web-services × 59
apache2 × 57
mod-rewrite × 56
amazon-ec2 × 54
rewrite × 54
reverse-proxy × 48
docker × 42
varnish × 42
permissions × 40
security × 39
ssl × 38
google-cloud-platform × 38 cache × 38