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),
same code works just fine and is
able to interact with the session just fine when the url-pattern is
/jsp/*. However as soon as the pattern is changed to /* the session
becomes unusable.
Rudy
On Wed, Sep 14, 2011 at 1:43 AM, Pid wrote:
> On 13/09/2011 23:35, Rudy Gireyev wrote:
>> If I
ow to do it.
> -Michael
> --- On Wed, 9/14/11, Rudy Gireyev wrote:
>
> From: Rudy Gireyev
> Subject: Re: HTTP errors Logging
> To: "Tomcat Users List"
> Date: Wednesday, September 14, 2011, 10:12 AM
>
> Hi Michael.
>
> Not sure if this is what you're asking,
In Eclipse, you do not run Tomcat on its own. It is configured as a
Server within Eclipse and then all of your programs that use Tomcat
will run within that Server.
1. To create a Server. Click File -> New -> Other and then expand the
Server category and select Server. Go through the wizard which
Hi Michael.
Not sure if this is what you're asking, but there's a logs directory
in your Tomcat installation directory. In it there should be several
log files that may contain a clue.
Rudy
On Wed, Sep 14, 2011 at 8:26 AM, Michael Gesundheit
wrote:
> Hi,
> I could not find anything in the arc
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
Savitha you forgot to mention what was the problem that you were having.
Anyway, in your realm specification, for the connectionName you need
to specify the actual name of the user (i.e. admin) that is able to
log into the LDAP to do the lookup that you are interested in.
connectionPassword is the
