http-status-code-301

I stupidly did a 301 redirect on websiteA.com to websiteB.com. After removing it from the .htaccess file the redirect is still in operation. I tried from outside the local network and it is still redirecting. I have cleared my cache and tried a different browser. Does anybody have any suggestions? UPDATE: If I add a 302 redirect to this .htaccess file the site honours it. When I remove it, the old 301 redirect still happens. .htaccess file for websiteA.com: # -- concrete5 urls start -- Options -Indexes <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f

I want to replicate what StackOverflow does with its URLs. For example: Hidden Features of C#? - ( Hidden Features of C#? ) or Hidden Features of C#? - ( Hidden Features of C#? ) Will Take you to the same page but when they return to the browser the first one is always returned. How do you implement the change so the larger URL is returned? The way that I've handled this before is to have two routes, registered in this order routes.MapRoute( null, "questions/{id}/{title}", new { controller = "Questions", action = "Index" }, new { id = @"\d+", title = @"[\w\-]*" }); routes.MapRoute( null,

I am using Scala dispatch HTTP library, version 0.10.1. I make a request to a URL that returns an HTTP 301, permanent redirect. For example, http://wikipedia.com returns a 301 that redirects to http://www.wikipedia.org/ . How do I do I use dispatch to get the redirected URL? Following the tutorial, here's what I've done. import dispatch._, Defaults._ val svc = url("http://wikipedia.com") val r = Http(svc OK as.String) r() This throws a "Unexpected response status: 301" exception. Presumably I need to either query the r value for the redirected URL, or maybe specify some argument other than OK

The RFC seems to suggest that the client should permanently cache the response: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 10.3.2 301 Moved Permanently The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise. The new permanent URI SHOULD be given by the Location field in

This seems ridiculous but I've not found a working answer in over an hour of searching. I have a static website running off nginx (which happens to be behind Varnish). The index file is called index.html . I want to redirect anyone who actually visits the URL mydomain.com/index.html back to mydomain.com . Here is my nginx config for the site: server { listen 8080; server_name www.mydomain.com; port_in_redirect off; location / { root /usr/share/nginx/www.mydomain.com/public; index index.html; } rewrite /index.html http://www.mydomain.com/ permanent; } http://www.mydomain.com/index.html responds

I have domain.com . If the user is logged in, it should load automatically domain.com/option-X where X is a predefined choice of the user. So, I do this at the top of index.php: header("Location: /option-X"); But, if the user is not logged in, I just choose automatically the first option like this: header("HTTP/1.1 301 Moved Permanently"); header("Location: /option-a"); So, i have two questions regarding the implications of doing so: Since the search engines crawlers won't be logged in, they will always get domain.com/option-a - does it affect them that it has a 301 header? What could be the