We're trying to connect to an OC4J server through HTTPS. We already got it working on HTTP, but it seems the client 'forgets' the session state when we connect to the same server in HTTPS. The first request goes fine, but after that it seems the state is lost.
The method we use to maintain session on the client side is by retaining the HttpState object throughout subsequent calls.
I assume that the session is referenced by a session ID in a Cookie. You should examine the Cookie store of the HttpState class and find out which cookies the server needs. Then you should check if those cookies are correctly transmitted to the server. Maybe the cookies are rejected by HttpClient because they are not specs conformant. Check the Log for warnings.
Also in my experience Oracle Appservers have a weird session management, especially when using Single Sign-on. I know of situations where sessions just got lost in between requests (with a normal web browser).
Odi
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
