Dear, I solved the cookie issues according to the article mentioned by Roland at http://www.nabble.com/forum/ViewPost.jtp?post=15912252&framed=y
After I "GET" a request to the server, the session will be established. The following sequences like POST a data or request any other pages by GET or POST will be in the right behavior. But if I "POST" a request with data to the server first instead of "GET", the following sequences just have different sessions and I will get a "Accessed Denied" warning. I think it's because the HttpClient library will store cookie after the "FIRST" GET request automatically, and will use it through the following browsing. If the "FIRST" request is a POST, the HttpClient won't store cookie for the following requests. Am I right ? or any hint? Sincerely, Micky -----Original Message----- From: micky [mailto:[EMAIL PROTECTED] Sent: Sunday, March 09, 2008 5:24 PM To: 'HttpClient User Discussion' Subject: RE: cookie or session-id is different from the same HttpClient connection?! Dear Oleg, > Because HttpClient does not find the first cookie when executing the > second request. You are not creating a new instance of HttpClient for >each request, are you? No, I am using the same instance of HttpClient for each request. Any suggestion for debugging? Sincerely, Micky --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
