302 Hijacks return!
Our very own JasonD posts about how the 302 nightmare scenario has come back to haunt us all. Great read, although youll need your full attention if your like me.
- 0 agreed / 0 disagreed
- Login to post comments
User login
Editors
*Active* Threadwatch Editors
Comments
wow
I shall have to look at that is some detail
This is GREAT STUFF
LOL!! I thought this issue was gone...
Jason, can you do me a favor and put a few more domainA, B, C and D's in there.. it's makes reading it more enjoyable :)
I aint sure if that's
I aint sure if that's sarcasm or not mate LOL :)
mmmm.... delicious reverse engineering....
if that doesn't get matt cutts' attention, i don't know what will ;)
Matt Bait?
I love it :)
am I stupid or smthn?
Will it be correct to sum up that Google as prone to 302 as before as I can see nothing that would not have entered the discussion since 2005 apart from may be the idea of studying the effects of 302 and using it as a Domain Status indicator
Correct me if I'm wrong PLZ
And another one bites the dust.
Countdown to when Goog ignores url shortening services.
10
9
8
7........