cookie conflict in Google Chrome Prerender
I used Chrome prerendering functionality using
<link rel="prerender" href="/path" /> But after lates updates, when I try to debug using [chrome://net-internals/#prerender] . This indicates that the pre-termination was interrupted due to the "Cookie Conflict" .
I tried debugging to make sure some ajax call changes cookies after the page loads, but did not find any. However, the prerender is interrupted. It worked great with previous chrome builds.
What you see is related to cookie conflicts.
Example:
Suppose a.com uses the greeting greeting = ... to indicate the greeting with which the user wants to greet.
Suppose the greeting is set to hello. We are prerender a.com/a.html , presenting " greeting = hello ." When the server generates the a.html file , it issues "hello" from the cookie on the web page that is previously transmitted.
Now, until a preview appears, suppose some other page on the greeting greets the greeting greeting = howdy Then, suppose the user goes to a.com/a.html. Prerender will be replaced. However, he saw a different version of the greetings cookie than the meaning it has now. Therefore, the page still displays “hello” and not (updated) “howdy”.
Inside, it keeps track of all the cookies that were detected during the preliminary listening (in the HTTP or javascript headers). If any of them is changed before the preview is shown, it will cancel the preview.
This kind of invalidity is what you have observed.