had mentioned it is not a
safe practice.
Thanks,
Kasra
- Original Message -
From: "Bill Barker" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, January 03, 2007 11:51 PM
Subject: Re: URL rewriting For Session Tracking
Usually you would use a tag lib for this sort of thin
En l'instant précis du 01/04/07 16:37, Caldarale, Charles R s'exprimait
dans toute sa noblesse:
>> From: David Delbecq [mailto:[EMAIL PROTECTED]
>> Subject: Re: URL rewriting For Session Tracking
>>
>
> Many thanks to Chris and David for the enlightenment.
&
> From: David Delbecq [mailto:[EMAIL PROTECTED]
> Of course, first is anyway incompatible with http based
> authentification, can only work on form based
> authentification (because browser caches the user/pass)
Not true - if the app uses in-memory session cookies (true for ASP,
ASP.Net and JSP)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
>> From: David Delbecq [mailto:[EMAIL PROTECTED]
>> Subject: Re: URL rewriting For Session Tracking
>
> Many thanks to Chris and David for the enlightenment.
>
> Another question: Ho
En l'instant précis du 01/04/07 16:32, fausto mancini s'exprimait dans
toute sa noblesse:
>
>
> David Delbecq wrote:
>
>> 2) in some cases it can be useful to have 2 sessions in same browser
>> (something you can't do with cookies)
>
> Hello David,
> I've never thought about that; it looks interest
Caldarale, Charles R wrote:
To step back a little: why would it be important to use URL encoding to
track sessions rather than do it with cookies?
Some log analyzers use such information to generate user profiles, etc.
--
Mikolaj Rydzewski <[EMAIL PROTECTED]>
smime.p7s
Description: S/MIME
> From: David Delbecq [mailto:[EMAIL PROTECTED]
> Subject: Re: URL rewriting For Session Tracking
Many thanks to Chris and David for the enlightenment.
Another question: How would one handle links embedded in static content?
Is it simply a matter of "don't do that&qu
> From: fausto mancini [mailto:[EMAIL PROTECTED]
> > 2) in some cases it can be useful to have 2 sessions in same browser
> > (something you can't do with cookies)
>
> Hello David,
> I've never thought about that; it looks interesting. Do you
> have a real use case for that?
Here's one: "Princi
David Delbecq wrote:
2) in some cases it can be useful to have 2 sessions in same browser
(something you can't do with cookies)
Hello David,
I've never thought about that; it looks interesting. Do you have a real
use case for that?
Thank you in advance.
_F_M
En l'instant précis du 01/04/07 16:04, Caldarale, Charles R s'exprimait
dans toute sa noblesse:
>> From: Christopher Schultz [mailto:[EMAIL PROTECTED]
>> Subject: Re: URL rewriting For Session Tracking
>>
>> I think you are misinterpreting the OP's question
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
> So setting cookies="false" in the element isn't sufficient?
That just tells Tomcat not to use cookies to send session identification
to the browser. Yes, the alternative to cookies is the use of URL
rewriting to
> From: Christopher Schultz [mailto:[EMAIL PROTECTED]
> Subject: Re: URL rewriting For Session Tracking
>
> I think you are misinterpreting the OP's question... I think
> he wants to /force/ the use of URL rewriting to include the
> jsessionid. In that case, he /must/ ru
[EMAIL PROTECTED] wrote:
All I want to do is 'URL rewriting For Session Tracking'. Do I have to do this
manually in my code (using response.encodeURL), or is there an automatic way of
doing this in Tomcat (such as using a filter or value) that would handle this
for me?
Add cookies="false" t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> Subject: Re: URL rewriting For Session Tracking
>>
>> Do I have to wrap every link that I have in my webapp with an
>>
ones. And that's my question; can I use the first syntax. Or
> there is no way but to use the second syntax if I want the session to be
> kept.
>
>
> Thanks,
> Kasra
> - Original Message -
> From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
e session to be
> kept.
>
>
> Thanks,
> Kasra
> - Original Message -
> From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
> To: "Tomcat Users List"
> Sent: Wednesday, January 03, 2007 9:56 PM
> Subject: RE: URL rewriting For Session T
on to be kept.
Thanks,
Kasra
- Original Message -
From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Wednesday, January 03, 2007 9:56 PM
Subject: RE: URL rewriting For Session Tracking
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: Re: URL rewriting For Session Tracking
>
> Basically I have a webapp and I want to have a session
> for each user that connects to my server (just the usual
> servlet session that is created with jsessionid). D
such a thing, or is seen as not a good practice.
I hope this makes my question clear.
- Original Message -
From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Wednesday, January 03, 2007 8:43 PM
Subject: RE: URL rewriting For
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: URL rewriting For Session Tracking
>
> All I want to do is 'URL rewriting For Session Tracking'.
I have to admit that I don't really understand your question. What do
you need to do with sessions that Tomcat doesn't already do
autom
20 matches
Mail list logo
