But what I want is request.getHeader.
-Original Message-
From: Peter Rossbach [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 11:56 AM
To: Tomcat Users List
Subject: Re: Problem with JK connector
You must used
JkEnvVar
You envVar can be accessed with
Unfortunately it doesn't work.
JkEnvVar is used for request.getAttribute(), instead of
request.getHeader()
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 10:19 AM
To: Tomcat Users List
Subject: Re: Problem with JK connector
Micha
ubject: Re: Problem with JK connector
Michael Li wrote:
Hi there,
Currently we use apache 1.3 and tomcat 4.1.31. We tried to connect
them through JK. Everything works fine, except some special http
headers are gone.=20 Because we user entrust direct, which will set
some special http header in the ht
* Chris Mooring wrote (18/01/06 15:11):
> Hi Michael,
>
> Could it be that your request headers are > 8K ? I was having some funny
> issues with JK2 this week where my page would suddenly show some sort of c
> stack trace about a BufferOverFlow Exception (we are no longer using JK2),
> but someone
not
be started
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 10:19 AM
To: Tomcat Users List
Subject: Re: Problem with JK connector
Michael Li wrote:
> Hi there,
>
> Currently we use apache 1.3 and tomcat 4.1.31. We tried t
". It looked like apache
server did it "intentionally".
-Original Message-
From: Chris Mooring [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 10:11 AM
To: Tomcat Users List
Subject: RE: Problem with JK connector
Hi Michael,
Could it be that your request head
Michael Li wrote:
Hi there,
Currently we use apache 1.3 and tomcat 4.1.31. We tried to connect them
through JK. Everything works fine, except some special http headers are
gone.=20 Because we user entrust direct, which will set some special
http header in the http request. The servlets will chec
Hi Michael,
Could it be that your request headers are > 8K ? I was having some funny
issues with JK2 this week where my page would suddenly show some sort of c
stack trace about a BufferOverFlow Exception (we are no longer using JK2),
but someone sent me this information;
"It looks like requests
