aakk9999 - 11:02 pm on Feb 22, 2013 (gmt 0)
I am working with eCom site where after certain time the (cookie based) session expires. Hence, if the user is on the site, walks away for 20 minutes, and then returns back to browse, the user gets message "session expired".
This is needed since after 20 minutes the cart user has been creating "expired", so that the user is aware they need to start to create cart again.
At the moment when this happens, the server responds with 302 sending the user on the page with "Session expired...(etc.)" message. The URL of such page has additional parameter ?requestedURL=aaaa where aaaa is the URL user attempted to go to when the session expired message is returned.
Having noticed that Google has picked up some of these URLs (perhaps via toolbar or similar), we have stopped this script being accessible to Google via robots.txt and as a backup added noindex in the head section.
Is there a better way to handle this situation?