Al Byers wrote:
In working with this problem I am seeing a difference in what the
BasicCookieStore stores and what is in the headers. Here is my code:
BasicHttpContext localContext = new BasicHttpContext();
// Create a local instance of cookie store
Al Byers wrote:
I was able to work around my problem by grabbing the JSESSIONID header out
of the first response and sticking it on the url of the second request. I
would prefer to find the right solution. When I take the JSESSIONID header
from the first response and add it as a header to the
In working with this problem I am seeing a difference in what the
BasicCookieStore stores and what is in the headers. Here is my code:
BasicHttpContext localContext = new BasicHttpContext();
// Create a local instance of cookie store
CookieStore cookieStore =
I was able to work around my problem by grabbing the JSESSIONID header out
of the first response and sticking it on the url of the second request. I
would prefer to find the right solution. When I take the JSESSIONID header
from the first response and add it as a header to the second request with:
I just signed on and found this in the archives:
On Fri, 2008-11-07 at 03:48 -0800, Eugene Kondrashev wrote:
I see..
But, how can I recognize the session id cookie?
I am afraid I do not have any good news for you.
In theory server can use any label to designate session id cookie. Is there
On Fri, 2008-11-07 at 03:48 -0800, Eugene Kondrashev wrote:
I see..
But, how can I recognize the session id cookie?
I am afraid I do not have any good news for you.
In theory server can use any label to designate session id cookie. Is there
some standard way to get sessionID cookie through
://www.nabble.com/Session-handling-in-HttpClient-tp18106268p20343451.html
Sent from the HttpClient-User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Well, sessions are server related. Let me give you an idea of how sessions work:
In this example I will use SESSID as the cookie name, but this can
be configured, and differs in all implementations.
First Request
1. Client visits server for the first time.
2. Server checks if the SESSID is set,
Hi Quitin,
Thanks for the response.
That does help me understand clearly about sessions.
I will try to implement the same and incase of any questions, will get back
to you.
Thanks again for your time.
Regards,
Jade
On Wed, Jun 25, 2008 at 12:47 PM, Quintin Beukes [EMAIL PROTECTED]
wrote:
