http-status-code-301

We have a couple of backends sitting behind our nginx front ends. Is it possible to intercept 301 / 302 redirects sent by these backends and have nginx handle them? We were thinging something alone the lines of: error_page 302 = @target; But I doubt 301/302 redirects can be handled the same as 404's etc etc... I mean, error_page probably doesnt apply to 200, etc error codes? So to summarize: Our backends send back 301/302s once in a while. We would like to have nginx intercept these, and rewrite them to another location block, where we could do any number of other things with them. Possible?

How do I go about redirecting all requests for domain.com/... to www .domain.com/... with a 301 in a django site? Obviously this can't be done in urls.py because you only get the path part of the URL in there. I can't use mod rewrite in .htaccess, because .htaccess files do nothing under Django (I think). I'm guessing something in middleware or apache conf? I'm running Django on a Linux server with Plesk, using mod WSGI The WebFaction discussion someone pointed out is correct as far as the configuration, you just have to apply it yourself rather than through a control panel. RewriteEngine On

I'm looking to redirect each and every page on the old domain to a single page on the new domain. It should also redirect both the www and non-www versions. Every single request to the domain old.com, whatever it may be, should lead to www.new.com root. old.com/1.php www.old.com/2.php old.com/2.php old.com/links/index.php old.com/about-us.html old.com/?string=1 should all redirect to: www.new.com/ I'm looking for a .htaccess solution. You can use RedirectMatch in the old.com vhost RedirectMatch permanent .* http://www.new.com/ Redirect appends the trailing portion of the matched URI to the

I have a few messy old URLs like... http://www.example.com/bunch.of/unneeded/crap?opendocument&part=1 http://www.example.com/bunch.of/unneeded/crap?opendocument&part=2 ...that I want to redirect to the newer, cleaner form... http://www.example.com/page.php/welcome http://www.example.com/page.php/prices I understand I can redirect one page to another with a simple redirect i.e. Redirect 301 /bunch.of/unneeded/crap http://www.example.com/page.php But the source page doesn't change, only it's GET vars. I can't figure out how to base the redirect on the value of these GET variables. Can anybody

I am trying to create a permanent htaccess redirect (301) from all files in one directory in one domain, to another domain as follows: Redirect all files in the following directory: http://www.primary.com/apples/* To: http://www.secondary.com I am not very experienced with htaccess and was wondering if someone can assist me in creating this redirect? Many thanks in advance! This should work in one .htaccess file at primary.com root directory: Options +FollowSymlinks -MultiViews RewriteEngine On RewriteBase / RewriteCond %{HTTP_HOST} ^www\.primary\.com [NC] RewriteRule ^apples/(.*) http://www

I'm running Apache 2.0 and I'm just wondering if it is possible to make a 301 redirect using JavaScript or jQuery. I have an <a></a> tag with href to a specified location and I'm asked to make a 301 redirect when I click that link. This is for SEO and I'm trying to find a way to do the 301 redirect to the same page in the link without having to create a new page or create a form/submit. In short No . JavaScript runs entirely on the client side. 301 redirects are supposed to come as a response from the server. Which means you cannot do this without server support. I know this is an old question

How do I 301 redirect, for example: a subdirectory /Blog/ to /blog/ with .htaccess? Sam Plus Plus Redirect 301 /Blog /blog Or use something like http://www.htaccessredirect.net/index.php The way that immediately comes to mind: RewriteEngine on RewriteBase /path/to/your/web/app RewriteRule ^Blog$ blog [R=301,L] RewriteRule ^Blog/(.*)$ blog/$1 [R=301,L] There are probably much better ways than mod_rewrite, and I'm not 100% sure that the external redirects will work as they should -- you may need the full URL -- but there you go. This is the simplest .htaccess solution, place it in /.htaccess: