Bugs item #669161, was opened at 2003-01-16 16:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669161&group_id=22866
Category: JBossWeb Group: v3.0 Rabbit Hole Status: Closed Resolution: None Priority: 5 Submitted By: J. Rhett Aultman (cuplan) Assigned to: Nobody/Anonymous (nobody) Summary: Jetty for 3.0.5 release giving null Session IDs Initial Comment: We have recently started using JBoss 3.0.5 and have noticed that the version of Jetty bundled with this release is giving out null session ids as a default behavior. Please advise. ---------------------------------------------------------------------- Comment By: Greg Wilkins (gregwilkins) Date: 2003-01-19 19:48 Message: Logged In: YES user_id=44062 This was actually a feature request as part of support for single sign on. If a session ID is offered - but that session does not exist, then it is used as the new session ID. So long as you use the session status to check if the session is new or not, this should not give you a problem. What is the scenario where it is giving you problems? Eitherway, I'll probably make this behaviour optional in the next release. ---------------------------------------------------------------------- Comment By: J. Rhett Aultman (cuplan) Date: 2003-01-17 19:37 Message: Logged In: YES user_id=132788 It should be noted that the suggested version of Jetty continued to give us session problems. In that particular case, Jetty was improperly assigning session IDs that should have been invalidated. Just a heads-up when selecting a version of Jetty to replace the default one with. ---------------------------------------------------------------------- Comment By: J. Rhett Aultman (cuplan) Date: 2003-01-16 18:06 Message: Logged In: YES user_id=132788 Many thanks for the fast and thorough response! ---------------------------------------------------------------------- Comment By: Greg Wilkins (gregwilkins) Date: 2003-01-16 17:37 Message: Logged In: YES user_id=44062 This bug was introduced with some session optimizations. It is already fixed in CVS head of Jetty, JBoss 3.0 and JBoss 3.2 A replacement jbossweb.sar will be available shortly. Alternatly you can grab the jetty 4.2.5 jar and drop that into your current jbossweb.sar. Details of how to do that are in the jetty/jboss FAQ: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669161&group_id=22866 ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
