On 6/17/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
> getPathInfo() might be interesting for this. Have you tried it Michael?
> I have use getPathInfo in my code but without setting up my appserver
> and running it I can't tell.
No, getPathInfo does not work. I guess I will just stick my own key
val
On 16/06/05 22:47 Max Cooper wrote:
I think this is a weird requirement, and it may be worth re-evaluating
why you want to know this (are you fighting the technology, or
leveraging it?). But here are two tips that might help if you decide
that you really need to know:
1. request.getPathInfo() --
ginal Message -
From: "Michael Jouravlev" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, June 16, 2005 12:28 PM
Subject: Re: [OT] Session ID in the URL
On 6/16/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
It seems to be hard-coded behaviour th
+1.
> From: Dave Newton [mailto:[EMAIL PROTECTED]
>
> Is anybody else getting a lot of message duplicates
> this evening? We're having email server strangeness
> so I'm not sure if it's me or... uh... not me.
-
To unsubscribe
Is anybody else getting a lot of message duplicates this evening? We're
having email server strangeness so I'm not sure if it's me or... uh...
not me.
Dave
Michael Jouravlev wrote:
On 6/16/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
Even quicker would be to check if you have the first requ
On 6/16/05, Max Cooper <[EMAIL PROTECTED]> wrote:
> I think this is a weird requirement, and it may be worth re-evaluating
> why you want to know this (are you fighting the technology, or
> leveraging it?).
I can explain but remember, that you asked it first ;) It will take some time :)
The point
I think this is a weird requirement, and it may be worth re-evaluating
why you want to know this (are you fighting the technology, or
leveraging it?). But here are two tips that might help if you decide
that you really need to know:
1. request.getPathInfo() -- the jsessionid might be a "pathInfo"
On 6/16/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
> Even quicker would be to check if you have the first request that
> establishes the session, and then put some token in the form or
> querystring, to mimic the JSESSIONID. Then you can just check
> for your token.
Yes, I guess I can do that.
> I
On 16/06/05 17:13 Adam Hardy wrote:
It seems to be hard-coded behaviour that you can't do anything about
unless you want to write some javascript to check the URL and put a
token in the query string for the next request.
Stupid me.
Even quicker would be to check if you have the first reque
On 6/16/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
> It seems to be hard-coded behaviour that you can't do anything about
> unless you want to write some javascript to check the URL and put a
> token in the query string for the next request.
Nah, I cannot rely on Javascript. I guess I should drop t
On 16/06/05 15:37 Michael Jouravlev wrote:
When both methods return true, they identify the first request after
session has been established with browser which supports cookies. I
try to keep GET requests clean to encourage browser to keep its page
history from growing. When I detect this request
On 6/16/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
> It's not stupid, it returns a boolean informing you where the
> session.getId() gets its info from. Makes sense to me.
Makes sense to me too, but I also want to know is there session ID in
the URL. Any advice how to find this out?
> Although you
On 16/06/05 05:51 Michael Jouravlev wrote:
Was celebrating too early. Does not work. Here what happens. * Very
first request to the app. Session is created on server. * Application
redirects to whatever location, server sets cookie with jsessionid in
the response, and at the same time adds jsessi
On 6/15/05, Dave Newton <[EMAIL PROTECTED]> wrote:
> David G. Friedman wrote:
>
> >See the HttpServletRequest API for these methods:
> >
> >boolean isRequestedSessionIdFromUrl() (pre 2.1)
> >boolean isRequestedSessionIdFromURL() (2.1 or later)
> >boolean isRequestedSessionIdFromCookie()
> >
> >
>
D'oh! Thanks, David!
On 6/15/05, David G. Friedman <[EMAIL PROTECTED]> wrote:
> See the HttpServletRequest API for these methods:
>
> boolean isRequestedSessionIdFromUrl() (pre 2.1)
> boolean isRequestedSessionIdFromURL() (2.1 or later)
> boolean isRequestedSessionIdFromCookie()
>
> Regards,
> D
David G. Friedman wrote:
See the HttpServletRequest API for these methods:
boolean isRequestedSessionIdFromUrl() (pre 2.1)
boolean isRequestedSessionIdFromURL() (2.1 or later)
boolean isRequestedSessionIdFromCookie()
This answer is better than mine :)
Must... keep... reading... JavaDocs..
: Wednesday, June 15, 2005 4:16 PM
To: Struts Users Mailing List
Subject: [OT] Session ID in the URL
Does anyone know, how to find out that URL contains session ID in it?
Usually this happens only once in the beginning of a session, if
browser supports cookies. I even don't need the value itself, I
Michael Jouravlev wrote:
Does anyone know, how to find out that URL contains session ID in it?
Session ID is separated with semicolon, and is not treated as query
parameter, so I cannot read as parameter.
Check for "sessionId" in getQueryString?
Dave
Does anyone know, how to find out that URL contains session ID in it?
Usually this happens only once in the beginning of a session, if
browser supports cookies. I even don't need the value itself, I just
want to know that fact, that session ID is appended to URL, not sent
as cookie.
Session ID is
19 matches
Mail list logo
