InternetExplorerDriver hijacking ASP.NET_SessionId Cookie
56 views
Skip to first unread message
eduardo sousa
Feb 28, 2012, 1:31:46 PM2/28/12
to Selenium Users
Hi everyone,
I've been using webdriver for the last few weeks (which was working
fine) and today I started having problems with the ASP.NET_SessionId
cookie. It works fine on the window where the test starts but when I
click on any element that opens in a new window I'm getting a
different SessionId back (at that point my webapp redirects me to the
login screen). The weird thing is that, if I start the test with
webdriver and let it fail, and then stop webdriver, close the window
and click on the element myself, I'll have my old functioning
SessionId back and everything works perfectly. It's just when the
InternetExplorerDriver is running that this happens. The webapp works
under normal conditions and it also works if I use a ChromeDriver
instead. Even funnier, is the fact that it always provides me with the
same "fake" SessionId everytime (kn3erwuqmrvla2re323tkjnt). I know
that SessionId get reused by IIS all the time, but you don't always
get the same one back, specially after reseting the app pool. Does
someone knows what might be causing this behaviour or how could I work
around it? Thanks in advance.
Best Regards,
Eduardo Sousa
I've been using webdriver for the last few weeks (which was working
fine) and today I started having problems with the ASP.NET_SessionId
cookie. It works fine on the window where the test starts but when I
click on any element that opens in a new window I'm getting a
different SessionId back (at that point my webapp redirects me to the
login screen). The weird thing is that, if I start the test with
webdriver and let it fail, and then stop webdriver, close the window
and click on the element myself, I'll have my old functioning
SessionId back and everything works perfectly. It's just when the
InternetExplorerDriver is running that this happens. The webapp works
under normal conditions and it also works if I use a ChromeDriver
instead. Even funnier, is the fact that it always provides me with the
same "fake" SessionId everytime (kn3erwuqmrvla2re323tkjnt). I know
that SessionId get reused by IIS all the time, but you don't always
get the same one back, specially after reseting the app pool. Does
someone knows what might be causing this behaviour or how could I work
around it? Thanks in advance.
Best Regards,
Eduardo Sousa
eduardo sousa
Feb 28, 2012, 5:48:05 PM2/28/12
to Selenium Users
Found it. I had a ie -noframe process running background. Point taken.
Reply all
Reply to author
Forward
0 new messages