> > We've been examining the headers, but the server doesn't seem to send
any
> > cookies (in http it does, but not in https). I was assuming this was
> > supposed to be done through some under-water process (I'm not very
familiar
> > with https), but the HttpState object does not contain any cooki
> 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
> b
Problem solved. It turned out to be the server.
We fixed it by installing Apache as an OC4J front-end, which coincidentally
also fixed another cookie-related bug we were working on.
Thanks for the help!
Arjan
-Original Message-
From: Dikhoff, A (ICT)
Sent: donderdag 23 oktober 2003 10:
Hello,
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 maintai
