Carl Nagle - 15/Feb/08 10:13 AM We are wondering if anyone has taken the chance to even look at or review this issue? The screenshots already provided suggest @sessionid@ is not valid syntax where found (as shown in attached console snapshots for both Firefox and IE7). The issue of Selenium Server not forwarding all needed content (like CSS) is very serious. It prevents our web applications from running correctly and, thus, from being able to use Selenium for test automation.

Carl Nagle - 15/Feb/08 12:38 PM I installed SVN and downloaded the latest source. The JARS we have are dated October 11, 2007. I see a sourcecode change happened in InjectionHelper.java on October 19, 2007 that may directly affect the behavior we are seeing. I will look for a snapshot dated after October 19, if one exists, and report back.

Carl Nagle - 18/Feb/08 02:05 PM The Snapshot I received still exhibits the same symptoms. Snapshot info: v0.9.3-SNAPSHOT [2172], with Core v0.8.4-SNAPSHOT [1950] I'm attaching the full debug log output which shows the Exception and Server Errors. The problem seems to occur when the first POST with a "seleniumStart=true" parameter and the sessionID parameter = "@SESSION_ID@". The full text of this post is: POST http://..../selenium-server/driver/?seleniumStart=true&localFrameAddress=top.frames[0]&seleniumWindowName=&uniqueId=sel_67606&sessionId=@SESSION_ID@&counterToMakeURsUniqueAndSoStopPageCachingInTheBrowser=1203362388297&sequenceNumber=0 HTTP/1.0 Which ultimately results in a SERVER ERROR response and a Connection Close: 14:19:48.313 WARN [11] org.mortbay.http.HttpConnection - POST http://..../selenium-server/driver/?seleniumStart=true&localFrameAddress=top.frames[0]&seleniumWindowName=&uniqueId=sel_67606&sessionId=@SESSION_ID@&counterToMakeURsUniqueAndSoStopPageCachingInTheBrowser=1203362388297&sequenceNumber=0 HTTP/1.0 java.lang.RuntimeException: sessionId @SESSION_ID@ doesn't exist; perhaps this session was already stopped? at org.openqa.selenium.server.FrameGroupCommandQueueSet.getQueueSet(FrameGroupCommandQueueSet.java:170) at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleBrowserResponse(SeleniumDriverResourceHandler.java:175) at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(SeleniumDriverResourceHandler.java:139) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) 14:19:48.485 DEBUG [11] org.mortbay.http.HttpConnection - RESPONSE: HTTP/1.1 500 Internal Server Error Date: Mon, 18 Feb 2008 19:19:48 GMT Server: Jetty/5.1.x (Windows XP/5.1 x86 java/1.5.0_08 Connection: close

Jeff Ramsdale - 23/Jul/08 03:33 PM I seem to be running into this problem as well. Any confirmation and/or progress?