>From the download page, http://httpd.apache.org/download.cgi (odd that
it's not on the front page):
"Important: Version 2.0.51 has a problem processing Satisfy directives
that may allow access to otherwise restricted areas. Please apply the
patch to fix this problem before using this version. A n
CAN-2004-0811 (cve.mitre.org)
Charlie
> -Original Message-
> From: Alex [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 24, 2004 4:00 AM
> To: Tomcat Users List
> Subject: RE: jk2 over non-default port
>
>
> what type of problems does 2.0.51 have??
>
what type of problems does 2.0.51 have??
On Thu, 23 Sep 2004, Kyle Adams wrote:
> Date: Thu, 23 Sep 2004 13:50:49 -0400
> From: Kyle Adams <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: jk2 over non-defa
> One thought is that your port number may be too high. I'm not
> sure what port range jk2 supports, but you may want to try something
> less than 32767.
Ding ding ding! That was the ticket!
Port 32767 works fine. Port 32768, and channelSocket.open() reverts
back to using the default 8009. B
t the logger level to debug and see if it provides anything
useful.
Charlie
> -Original Message-
> From: Kyle Adams [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 23, 2004 9:49 AM
> To: [EMAIL PROTECTED]
> Subject: RE: jk2 over non-default port
&
> add under your [channel.socket:localhost:60002]
> host=localhost
> port=60002
According to the documentation at
http://jakarta.apache.org/tomcat/connectors-doc/jk2/jk2/configwebcom.html
(under channel.socket):
"The name of the channels should be: channel.socket:HOST:PORT, where
HOST and PORT ar
> -Original Message-
> From: Kyle Adams [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 22, 2004 5:49 PM
> To: [EMAIL PROTECTED]
> Subject: jk2 over non-default port
>
> I've been able to get jk2 running if I use the default port; however, I
> get these error messages if I try to
