struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ana Narvaez Vila" <>
Subject Re: URGENT RE: token issue in hyperlink
Date Wed, 07 Mar 2001 18:14:49 GMT
I think you must disable the cookies of your browser

"Nanduri, Amarnath" wrote:
>    I was able to see the Token . I am talking about the jsessionid that will
> be created for a hyperlink. If the <html:link> tag is used, it automatically
> re-writes the url to include a jsessionid. I was unable to see this. Thanks.
> cheers,
> Amar..
> -----Original Message-----
> From: Michael McCallister []
> Sent: Wednesday, March 07, 2001 12:23 PM
> To:
> Subject: RE: URGENT RE: token issue in hyperlink
> I can't speak about the address bar (different browsers probably behave
> differently), but if you aren't seeing it in the generated source then
> there is a problem.  To confirm, you don't see the
>          org.apache.struts.taglib.html.TOKEN=4bb7c9e6084fbf88acc2aa976ea9e3
> string in your generated hyperlink href?  Do you see the
> "org.apache...TOKEN" part but not the hex string after the equals sign?  If
> so, maybe you are not doing a saveToken(request) in an Action before you
> forward to your JSP page.
> Mike
> At 10:58 AM 3/7/2001, you wrote:
> >Mike,
> >
> >        Thanks a lot. It works. I did vote for this enhancement to take
> >place. One question i have come i don't see the session id in the
> >address bar ? Is it because GET limits the number of characters that can be
> >kept in the Address Bar ? Also i did not see the sessionid when i did a
> >'view source' and checked the source of my generated page. Clarification on
> >this issue is greatly appreciated.
> >
> >cheers,
> >Amar..
This email is confidential and intended solely for the use of the individual to whom it is
addressed. Any views or opinions presented are solely those of the author and do not necessarily
represent those of Sema Group. 
If you are not the intended recipient, be advised that you have received this email in error
and that any use, dissemination, forwarding, printing, or copying of this email is strictly

View raw message