I got the same problem here with the sample?.html files: "Invalid auth
token", and it might be a PHP shindig only problem i have here that
coincidentally gives the same error, but maybe it's not coincidence so
i'll post what i've found here anyhow :)
Basically what i've found with some console.log'ing is that on a first
page load (or forced reload) i get (console.log("auth comp:
"+authToken[rpc.f]+" = "+rpc.t);)
auth comp: 1185834238 = 1185834238
but when i do a 'soft reload' (so no forced reload) i get:
auth comp: 201272794 = 1185834238
So it's still using the old token from the previous request, hence the
token's aren't identical, and you get an auth token error.
Since the original report said that when Arne changed the URL it
worked, now it might not have been a absolute vs relative URL problem,
but just have forced the browser to reload the frame's, and hence
working again (a second refresh after that would've shown i think that
it was still 'broken')
-- Chris
On Mar 7, 2008, at 9:45 PM, Kevin Brown wrote:
It shouldn't -- auth token validation is based on the iframe id, not
the
url. I'll take a look.
