Hi,
Thanks for that - it solved my problem neatly ...
I'd also like to say thanks to the list - great to see a big community
that helps out so quickly and politely!
Thnks
Mike
On Thu, 03 May 2007 15:46:18 +0100
Richard Kirby <[EMAIL PROTECTED]> wrote:
> Hi Mike,
>
> I think you will find that the cookie used for session tracking is
> actually generated by the servlet engine
> (Tomcat/Jetty/Weblogic/whatever) and nothing to do with Tapestry.
>
> However, since cookies are nothing but HTTP header lines, you could
> always use a Filter to hack the cookie header line. Alternatively, if
> you are using mod_proxy to hook your apache to your servlet engine,
> look into using ProxyPassReverseCookiePath and
> ProxyPassReverseCookieDomain.
>
> Cheers
>
> Richard
>
> Mike Davis wrote:
> > Hi,
> >
> > As it turns out, the problem is actually that I've used Apache's
> > mod_rewrite to transparently eliminate the context part of the path
> > ('/xyz/app.htm' => '/app.htm') and obviously Tapestry uses the
> > context as part of the cookie's path ...
> >
> > Is there a way to setup Tapestry so that it will set up the cookie
> > path without the context (or with an alternate path)? I have other
> > applications on the same app server, so I still need to keep the
> > apps in seperate contexts.
> >
> > I have taken a look in the code and I suppose I could simply hack it
> > until it works, but obviously I'm hoping that it's possible just
> > using a config file.
> >
> > Thanks
> > Mike Davis
> >
> >
> > On Thu, 3 May 2007 08:47:10 +0200
> > Mike Davis <[EMAIL PROTECTED]> wrote:
> >
> >
> >> Hi,
> >>
> >> The problem is that I have a page that I'd like users to be able to
> >> access with or without a session. This works fine, but calling
> >> getVisit() on that page returns null whether or not the user
> >> previously had an accessible visit object. Once a user has been to
> >> that page, calls to getVisit() from *any other page* also return
> >> null, again regardless of whether a visit object was previously
> >> accessible.
> >>
> >> Thanks
> >> Mike Davis
> >>
> >>
> >>
> >> On Thu, 3 May 2007 04:50:29 +0300
> >> "Andreas Andreou" <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>> not, that's not correct... session is not invalidated when
> >>> clicking on a DirectLink having the stateful flag set to false
> >>>
> >>> What exactly is the problem you're facing?
> >>>
> >>> On 5/3/07, Mike Davis <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> I've been asked to do some work on a Tapestry 3 application
> >>>> (unfortunately I can't upgrade it!) and I'm struggling with a
> >>>> DirectLink/session issue. I would like to allow our users to
> >>>> access certain pages without session, yet still be able to return
> >>>> to pages that require a session, without losing any stored state.
> >>>>
> >>>> Is it possible to create a Tapestry app that allows a user to do
> >>>> the following?
> >>>> - open a page that creates and uses a visit object
> >>>> - click a DirectLink with the stateful flag set to false
> >>>> - go back to the first page and use the original visit object
> >>>> again
> >>>>
> >>>> Is it correct to say that once a DirectLink is clicked with the
> >>>> stateful flag set to false, any session data associated with that
> >>>> user's session is invalidated?
> >>>>
> >>>> Thanks
> >>>> Mike Davis
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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]
