Installation issue - HTTPS connector always sends junk reply

2004-07-08 Thread Jason
Howdy.
I'm new to Tomcat, and I'm having a bit of trouble finishing a setup
for testing.  I've set up the default installation - that is,
unzipped it and run the batch file - and it works very well.  However,
the ride gets a bit bumpy when I try to enable HTTPS connections.

After generating the .keystore file and uncommenting the default port
8443 connector, Tomcat seems to start fine.  The only notable difference
is that a new connector is created (that should be a good sign).  When
I connect to my server at localhost using port 8443, though, it sends
me a small piece of garbage in return.  It always seems to be the same
chunk of binary data; it looks like this (hexdump on x86):
1503 0100 0202 0a.  Connections to port 8080 continue to work as
advertised; connections to other (random) ports fail as expected.

I've followed the instructions on setting up SSL several times.  I've
got a .keystore file in my home folder, and the HTTP connector is the
default included with the Tomcat 5 binaries (sans comments).  I'm open
to the possibility that I'm repeatedly missing a step, of course.

I've tried Tomcat 5.0.25 and .27 on both Windows 2000 and Linux, using
IE and Firefox as clients; always the same results.  The JVM is Sun's
1.4.2_04 on Linux, and 1.4.1_02 on Windows.

Thanks for any help,
Jason

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Installation issue - HTTPS connector always sends junk reply

2004-07-08 Thread Jason
=== Thu, Jul 08, 2004 at 08:32:21PM -0500 / Jason ===
 Howdy.
 I'm new to Tomcat, and I'm having a bit of trouble finishing a setup
 for testing.  I've set up the default installation - that is,
 unzipped it and run the batch file - and it works very well.  However,
 the ride gets a bit bumpy when I try to enable HTTPS connections.
 
 After generating the .keystore file and uncommenting the default port
 8443 connector, Tomcat seems to start fine.  The only notable difference
 is that a new connector is created (that should be a good sign).  When
 I connect to my server at localhost using port 8443, though, it sends
 me a small piece of garbage in return.  It always seems to be the same
 chunk of binary data; it looks like this (hexdump on x86):
 1503 0100 0202 0a.  Connections to port 8080 continue to work as
 advertised; connections to other (random) ports fail as expected.
 
 I've followed the instructions on setting up SSL several times.  I've
 got a .keystore file in my home folder, and the HTTP connector is the
 default included with the Tomcat 5 binaries (sans comments).  I'm open
 to the possibility that I'm repeatedly missing a step, of course.
 
 I've tried Tomcat 5.0.25 and .27 on both Windows 2000 and Linux, using
 IE and Firefox as clients; always the same results.  The JVM is Sun's
 1.4.2_04 on Linux, and 1.4.1_02 on Windows.
 
 Thanks for any help,
 Jason
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
=== End Quote ===

Pre-answered in another mail; thanks!

Jason

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Fake https connector

2003-10-23 Thread Norris Shelton
We use BigIP to perform SSL duties for our website.  We are
about to add a filter to force all page accesses to be sure.

The plan is to have two ports (9000 for regular requests and
11000 for secure requests).  It would work like this:
Request comes in on port 80 to BigIP.  It would send the request
to port 9000 on the tomcat.  The filter would check the scheme. 
It is not https, so it would redirect to the same URL with the
scheme of https.

BigIP would receive the redirected request on port 443.  It
would decrypt it and send it to port 11000.

I see where it has the scheme and secure parameters on the
standard connector.  I was thinking that I could use a regular
connector, but change scheme to https.  This would give my
filter what it needs and still allow BigIP to perform
decryption.

However, when I do this, requests to https (443) hang.  They
never get through.  

Any ideas?



=

Norris Shelton
Software Engineer
Sun Certified Java 1.1 Programmer
Appriss, Inc.
ICQ# 26487421
AIM NorrisEShelton
YIM norrisshelton


__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Https Connector

2001-04-05 Thread Rams

Hi all,
This is the default HttpConnector.

Connector className="org.apache.tomcat.service.PoolTcpConnector"
 Parameter name="handler"
 
value="org.apache.tomcat.service.http.HttpConnectionHandler"/
 Parameter name="port"
 value="8080"/
/Connector

ls there any HttpsConnector that comes with Tomcat?

-Rams


 winmail.dat