Databases
StackOverflow2013
Postsdbo
POSharing Sessions with 302 Redirects/IMG SRC/ JSON-P and implications with Google SEO/Pagerank or Other Problems
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSharing Sessions with 302 Redirects/IMG SRC/ JSON-P and implications with Google SEO/Pagerank or Other Problems
    primarykey
    data
    text
    <p>I am currently researching the best way to share the same session across two domains (for a shared shopping cart / shared account feature). I have decided on two of three different approaches:</p> <p>Every 15 minutes, send a one time only token (made from a secret and user IP/user agent) to "sync the sessions" using:</p> <ol> <li><p>img src tag</p> <p>img src="http://domain-two.com/sessionSync.png?token="urlsafebase64_hash"</p> <ul> <li><p>displays an empty 1x1 pixel image and starts a remote session session with the same session ID on the remote server. The png is actually a PHP script with some mod_rewrite action.</p></li> <li><p>Drawbacks: what if images are disabled?</p></li> </ul></li> <li><p>a succession of 302 redirect headers (almost same as above, just sending token using 302's instead:</p> <ul> <li>redirect to domain-2.com/sessionSync.php?token="urlsafebase64_hash"</li> <li><p>then from domain-2.com/sessionSync, set(or refresh) the session and redirect back to domain-1.com to continue original request. </p></li> <li><p>QuestionL What does Google think about this in terms of SEO/Pagerank?? Will their bots have issues crawling my site properly? Will they think I am trying to trick the user?</p></li> <li><p>Drawbacks: 3 requests before a user gets a page load, which is slower than the IMG technique.</p></li> <li>Advantages: Almost always works?</li> </ul></li> <li><p>use jsonp to do the same as above.</p> <ul> <li>Drawbacks: won't work if javascript is disabled. I am avoiding this option because of particularly this.</li> <li>Advantages: callback function on success may be useful (but not really in this situation)</li> </ul></li> </ol> <p>My questions are:</p> <ul> <li>What will google think of using 302's as stated in example 2 above? Will they punish me?</li> <li>What do you think the best way is?</li> <li>Are there any security considerations introduced by any of these methods?</li> <li>Am I not realizing something else that might cause problems?</li> </ul> <p>Thanks for all the help in advance!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChristian Scarlet
    1. USChristian Scarlet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSharing Sessions with 302 Redirects/IMG SRC/ JSON-P and implications with Google SEO/Pagerank or Other Problems
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSharing Sessions with 302 Redirects/IMG SRC/ JSON-P and implications with Google SEO/Pagerank or Other Problems
      1. USregilero
      1. VTFavorite
    1. COI prepared a paper on this, going into quite a bit of detail. I'll post it here as an answer when I have time, or contact me for it.
      singulars
      1. POSharing Sessions with 302 Redirects/IMG SRC/ JSON-P and implications with Google SEO/Pagerank or Other Problems
      1. USChristian Scarlet
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload