Marco et al,

That's great. I've always wondered how you handle those Cookieless browsers.
Another tool goes into my toolbox...

Thanks, Upayavira

On 14 Aug 2003 at 10:01, Marco Rolappe wrote:

> hi upayavira,
>
> there's no special treatment necessary if you let the servlet engine
> handle sessions. at least in the case of tomcat, the sessionid is
> encoded as a path segment parameter (see RFC2396 -> 3.3. Path
> Component), like e.g.:
>
> http://foo.com/bar.xhtml;jsessionid=<sessionid>
>
> the request URL reaching the web applications (cocoon, ...) doesn't
> contain the sessionid, so yes, the URL rewriting is (kind of) undone.
>
> as long as you let the servlet engine handle sessions, they are (more
> or less) transparent to you.
>
> > -----Urspr�ngliche Nachricht-----
> > Von: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]
> > Auftrag von Upayavira Gesendet: Donnerstag, 14. August 2003 09:34
> > An: [EMAIL PROTECTED] Betreff: Re: AW: session cookies
> >
> >
> > Thanks for this clarification. Very useful. And what do you need to
> > do to your sitemap matchers to handle incoming URLs that have been
> > rewritten? Anything? Or is the URL rewriting undone before the URL
> > is given to Cocoon?
> >
> > Thanks, Upayavira
> >
> > > hi sonny,
> > >
> > > the check is automatically done by the servlet engine; if the
> > > user's browser doesn't accept cookies, sessions are realized by
> > > rewriting URLs. you have to send your URLs through the servlet
> > > engine's encodeURL/encodeRedircetURL though.
> > >
> > > but the good news is that you can use cocoon's
> > > EncodeURLTransformer, which does this automatically; you just give
> > > it a pattern that matches elements' attributes that will be
> > > treated as URLs to be encoded.
> > >
> > > HTH
> > >
> > > > -----Urspr�ngliche Nachricht-----
> > > > Von: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]
> > > > Auftrag von Sonny Sukumar Gesendet: Donnerstag, 14. August 2003
> > > > 07:40 An: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > > Betreff: RE: session cookies
> > > >
> > > >
> > > >
> > > > Hmmm, how does one determine that the user doesn't have cookies
> > > > enabled and then switch the whole app over to using URL
> > > > rewriting? That seems like a daunting task.
> > > >
> > > > >From: "neil" <[EMAIL PROTECTED]>
> > > > >
> > > > >See
> > > > >http://cocoon.apache.org/2.1/userdocs/transformers/encodeurl-tr
> > > > >an
> > > sformer.html
> > > >
> > > >You can use session cookies if the browser allows them and if it
> > > >doesn't you can encode the session id in your apps URLs. There's
> > > >no need to lose users that don't like cookies.
> > > >
> > > >
> > > >-----------------------------------------------------------------
> > > >---- To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > >For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > >
> > > _________________________________________________________________
> > > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
> > > http://join.msn.com/?page=features/virus
> > >
> > >
> > > ------------------------------------------------------------------
> > > --- To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > > ------------------------------------------------------------------
> > > --- To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to