Hi Volker,
Yes thanks, this should Work. I know about the Session Cookie.
But my Problem was a CSRF filter in our Tapestry app, which I Not
recognized directly :-)
All is fine now, thanks again.
Volker Lamp schrieb am Mi., 27. Apr. 2022, 16:40:
> Hello Eric
>
> Not sure about the setup of your application server, but likely the
> session id is stored in a cookie. So when your users return to your
> Tapestry app (in whatever way, e.g. using the browser's back-button;
> clicking a hyperlink; or typing the URL into the browser's address field)
> their browser will present the session id from the cookie and on they go
> (unless, of course, the session hasn't expired yet).
>
> If the page they are supposed to return to depends on the circumstances,
> you could pass the url for the current Tapestry page to the other app as a
> request parameter. Something like
> https://otherapp/otherpage?returnTo=urlOfTapestryAppToReturnTo.
>
> Hope this helps.
>
> Volker
>
>
>
> On 2022/04/27 12:51:15 Ric 2000 wrote:
> > Hi all,
> >
> > I'm struggling with the following Situation:
> >
> > From my Tapestry application with active http session I call a page in
> > another non Tapestry application in the same browser tab.
> >
> > But after that I want to navigate back from that application to the
> > original Tapestry page.
> >
> > I guess it should be a normal hyperlink, but how must the URL look like?
> > Must it contain certain parameters like a session ID?
> >
> > Thank you very much for your help.
> >
> > Regards, Eric
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
