Yes, I just wasn't sure about the semicolon, but I guess it is fine. REST needs to be fixed then.
musachy On Sun, Jun 15, 2008 at 1:31 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Sat, Jun 14, 2008 at 3:48 PM, Dave Newton <[EMAIL PROTECTED]> wrote: > >> Not sure about WAS, but don't (at least) Tomcat and Resin do that (a) before >> it knows if cookies are enabled, and (b) if cookies aren't enabled? > > It's part of the Servlet spec. Tracking by cookies is required. If > the client won't accept a cookie, the container may do url rewriting, > and if it chooses to do so, it must use a path parameter called > jsessionid. (SRV.7.1.3) The container is required to support > sessions for clients that do not accept cookies. While the spec > doesn't mandate url rewriting, it does say containers commonly support > it. > > I'm curious what difference you're seeing between Jetty and Tomcat? > It sounds like Tomcat stops appending the jsessionid, but Jetty > continues doing it? That's certainly valid (at least for the first > response)... perhaps the framework needs to deal with it better? > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
