Would you be able to share the site URL you are testing, if it's public? For reproducing issue.
In the meantime, as a workaround, could you not manually set the cookie via Selenium to continue testing? Not ideal, but it would at least allow you to proceed.
On Wednesday, May 22, 2013 12:39:37 PM UTC-7, Joe Shaw wrote:
Hi,
I just came across some behavior with cookies that seems to be inconsistent between WebDriver and the browser, and could use some guidance.
The server I am hitting is setting a cookie for the same name twice, first deleting/expiring it and then setting it again. For example:
Set-Cookie:flash=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; domain=.
example.comSet-Cookie:flash=LoremIpsum; path=/; domain=.
example.com
The browsers (both Chrome 27 and Firefox 21) send the "LoremIpsum" cookie on subsequent requests. Neither the Chrome nor Firefox Selenium drivers do, and the site throws an error because it requires this cookie to work.
I'm not sure if setting the same cookie twice in the same request this way is kosher, but unfortunately the site I am hitting is not under my control. (I am testing an OAuth login flow through a third-party site.) I couldn't find any literature on whether the behavior of this is defined, but it seems like Selenium should behave as both Chrome and Firefox do. Have others seen this? Would folks consider this a bug? Has a bug been filed?
Thanks,
Joe