We all know about the issue of the dreaded 302 redirect from one site to another, I was just wondering if anyone had any experience when it comes to 302's being used from one page in a site to another page within the same site. For instance... site.com/directory/ redirecting the user to site.com/directory/default.html (Don't ask why it's like that) Any help is most appreciated. Cheers
302 or 303 is what you would normally use for things like a receipt page after the customer has completed an order form. This way the customer can refresh the receipt page all they want without ending up submitting multiple orders. There are other uses of 302 within a website as well. You may temporary promotional pages, temporary under construction pages, etc. J.D.
I understand that, but what I wanted to know, was whether or not Google will have a problem with the use of a 302 if it's within the same site? Thanks for the response (I guess this should actually be in the google forum).
The 302 is dangerous to use even on your own domains, or within your site as long as Google ignores this: http://clsc.net/research/google-302-page-hijack.htm Help stop this: http://www.darrinward.com/google302/ As for within your own site, look at this thread: http://forums.digitalpoint.com/showthread.php?t=16232 Specifically, the post I made about gldir messing up it's own sales site.
If Google doesn't have a problem following hijacking redirects, it surely won't have one following those within your domain Seriously, though, 302 is just a way to redirect clients so that the response is handled in a certain way by all parties (e.g. no caching by the proxies, etc). I can't imagine why would any SE punish any website for using 302 within the same domain. J.D.
Neither can I. But I also can't see any reason for them to punish sites that have 302's pointing to them. This is wy I wanted to check on whether there could be any adverse effects.
There's a reason why Google isn't "fixing" this problem. Without establishing domain ownership, there is really no reliable way to determine whether a redirection code is used illegitimately. Most HTTP servers will use 302 for redirection if no explicit code is specified (e.g. Response.Redirect in ASP, [R] in mod-rewrite, etc), so there are tons of legitimate domains that will return 302 pointing to a domain alias. J.D.
Agreed 100%, but that doesn't negate the fact that we as webmasters still have to deal with the issue, because of a few wankers. I guess life's like that though.
I am trying to use a 302 redirect to retreive all of the search engine ranking of a site that was given to me. The owner doesn't remember his password since he let it sit so long. Now a competitor is doing the same thing and has a redirect going also!!! Scum! I received the site legitimately and this guy at golf ball zone is trying to hijack!!!