New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GetCookies sometimes fails on chromedriver #14
Comments
Thanks for reporting this. It looks like we might need to use |
I'm happy to make the changes, but this looks like it will break the API. Is that cool? |
Fine with me. Thank you! |
Bowbaq
added a commit
to Bowbaq/go-selenium
that referenced
this issue
Oct 8, 2015
…ng chromedriver Chrome appears to store cookies with an expiry time that can include milliseconds. When using the chromedriver, this internal representation is returned (ie. Expiry: 1475462515.303742) which causes the Go json parser to fail. This fixes the issue by avoiding deserializing the Expiry field upfront, and handling it separately.
This was referenced Oct 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that when using ChromeDriver (and perhaps other drivers), sometimes the value returned for the cookie's
expiry
field doesn't deserialize as auint
.For example:
Notice how the
expiry
field has a period followed by a bunch of digits. I'm guessing this is fractions of a second?I changed the type of
Expiry
tointerface{}
in my fork to fix the immediate issue. Maybe there is a way to detect this & handle it better though.The text was updated successfully, but these errors were encountered: