sportsguy
03-01-2007, 06:25 PM
OK, so we recently implemented a common login system across all our main websites.
The problem now, is that we are seeing 302 redirects.
When a user shows up, they are passed to an "accounts" server, which determines if they have a cookie or not. If yes, they go back to the requested URL with a parameter added to the URL.
If no, they go to the requested URL with a different parameter added to the URL.
So, the issues, as I see them, are:
1 - we're seeing 302 redirect codes in the header (using a header checker tool, that is)
2 - since the URL is physically changing, I think we're seeing a dupe content issue as well (same actual content on a page, yet the URL is different
Here's the path the redirections take:
1 - users is sent to the account server - seen as a 302
2 - user is sent back to the production server (live server) - seen as a 302
3 - page loads form the live server, and the code is seen, at this last point, as a 200
So, in essence, there's 2 hops being made via 302s, then the page finishes loading and returns the final code as a 200.
Now, since we implemented this change, we've seen PR drop to zero.
The next step is supplemental pages and loss of traffic - not an option as G is 70% + of inbounds.
My code guys are working on this from there end.
Anything else I should be looking at?
How does the 302 spammers use work? (Could someone be targeting us, basically?)
The problem now, is that we are seeing 302 redirects.
When a user shows up, they are passed to an "accounts" server, which determines if they have a cookie or not. If yes, they go back to the requested URL with a parameter added to the URL.
If no, they go to the requested URL with a different parameter added to the URL.
So, the issues, as I see them, are:
1 - we're seeing 302 redirect codes in the header (using a header checker tool, that is)
2 - since the URL is physically changing, I think we're seeing a dupe content issue as well (same actual content on a page, yet the URL is different
Here's the path the redirections take:
1 - users is sent to the account server - seen as a 302
2 - user is sent back to the production server (live server) - seen as a 302
3 - page loads form the live server, and the code is seen, at this last point, as a 200
So, in essence, there's 2 hops being made via 302s, then the page finishes loading and returns the final code as a 200.
Now, since we implemented this change, we've seen PR drop to zero.
The next step is supplemental pages and loss of traffic - not an option as G is 70% + of inbounds.
My code guys are working on this from there end.
Anything else I should be looking at?
How does the 302 spammers use work? (Could someone be targeting us, basically?)