RFC doesn’t specify any referrer-specific behavior in status 301 definition, nor 301-specific behavior in Referer header definition. Thus, I have to say that although this referrer-preserving behavior is logical, it is not defined in RFC and thus you can never be sure.
According to https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#server-name-if, you should use: server { server_name www.example.com; return 301 $scheme://example.com$request_uri; } server { server_name example.com; # […] }
I came up with the solution and posted it on my blog http://web.archive.org/web/20130310123646/http://onlinemarketingexperts.com.au/2013/01/how-to-permanently-redirect-301-all-404-missing-pages-in-htaccess/ here is the htaccess code also RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-f RewriteRule . / [L,R=301] but I posted other solutions on my blog too, it depends what you need really
I know this is an old question but the answers don’t really address the primary issue that was presented in the question which is a 301 redirect for SEO purposes (and the answer today may very well be different than it was when the question was originally asked and answered). The answer that no, you … Read more
Using a 307 should be exactly what you want 307 Temporary Redirect (since HTTP/1.1) In this case, the request should be repeated with another URI; however, future requests should still use the original URI.[2] In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original … Read more
RedirectMatch uses a regular expression that is matched against the URL path. And your regular expression /contact.php just means any URL path that contains /contact.php but not just any URL path that is exactly /contact.php. So use the anchors for the start and end of the string (^ and $): RedirectMatch 301 ^/contact\.php$ /contact-us.php
The effect of the 301 would be that the search engines will index /option-a instead of /option-x. Which is probably a good thing since /option-x is not reachable for the search index and thus could have a positive effect on the index. Only if you use this wisely After the redirect put exit(); to stop … Read more
I resolved this by opening dev tools (F12), click “Network”, then click the “Preserve log” checkbox, and make the request that results in the cached 301. Right-click the request that results in the 301 and click “clear browser cache”. Try again and then 301 should no-longer be cached.
The best solution is to use both <meta http-equiv=”refresh” and <link rel=”canonical” href= It works very well, Google Bot reindexed my entire website under new links without losing positions. Also the users are redirected to the new posts right away. <meta http-equiv=”refresh” content=”0; url=http://konradpodgorski.com/blog/2013/10/21/how-i-migrated-my-blog-from-wordpress-to-octopress/”> <link rel=”canonical” href=”http://konradpodgorski.com/blog/2013/10/21/how-i-migrated-my-blog-from-wordpress-to-octopress/” /> Using <meta http-equiv=”refresh” will redirect each visitor … Read more
In the absense of cache control directives that specify otherwise, a 301 redirect defaults to being cached without any expiry date. That is, it will remain cached for as long as the browser’s cache can accommodate it. It will be removed from the cache if you manually clear the cache, or if the cache entries … Read more