Thank you for your reply Konstantin.
> In short:
> 1. When session cookie is created in recent versions of Tomcat, the
> Path parameter in it is set to webappName + "/".
>
> 2. Requests to "webappName" are usually automatically redirected to
> "webappName + /" (Tomcat sends response code 302),
2011/9/14 Rudy Gireyev :
> Thank you P for the response. I admit I don't 100% understand what you mean by
> "Sounds like the session isn't being maintained in between requests."
> Is this something that I'm doing wrong? Or is this something outside
> of my control?
>
> The strange thing is that thi
Thank you P for the response. I admit I don't 100% understand what you mean by
"Sounds like the session isn't being maintained in between requests."
Is this something that I'm doing wrong? Or is this something outside
of my control?
The strange thing is that this very same code works just fine and
On 13/09/2011 23:35, Rudy Gireyev wrote:
> If I change the url-pattern to /* then the user is authenticated each
> and every time the application is accessed and the
> request.getRemoteUser() is then set to that user name. But then I
> cannot store anything in the session of the application. When I
I've run into a problem that I can't seem to resolve. :( I have to
configure Tomcat to work with Microsoft LDAP. I'm using Tomcat 7, and
both servers are running on Windows 2003. I managed to configure a
JNDI Realm in server.xml and it seems to be able to connect to LDAP
and authenticate the user w
