Hi,
Actually, it has nothing to do with SSL...
We took out https portion, it still resulted in same "Bad envelope tag: html" error.
So this must be Apache in the middle...
Our set up with Axis Client -> Tomcat/Axis Server works great.
However,
If we introduce Apache in the middle for redirecting so that
client side server side
-------------- -------------------
Axis Client -> ~~~~ -> Apache web server -> Tomcat/Axis Server, we get following
error...
Has anybody experienced with Apache web server in the middle?
(by the way, this Apache redirecting works great for other non-axis web applications,
so this set up is valid)
We have to use Apache web server in the middle since we like to do basic auth and SSL
handling on it eventually..
Thanks for your time.
Lee
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad envelope tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Bad envelope
tag: html
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:70)
-----Original Message-----
From: insoo lee [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 9:57 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Axis/SSL with Apache/Tomcat
Hi,
we are trying to do basic auth with SSL/HTTPS.
Our Axis client is invoking a method deployed by Axis server running in
Tomcat. We have Apache web server that sits in front of Tomcat and Apache
web server handles basic auth and SSL. Basic auth is working great using
call.setUsername and call.setPassword. However, when using SSL, it complains
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad envelope tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Bad envelope tag: html
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:70
)
at
org.apache.axis.encoding.DeserializationContextImpl.startElement(Deserializa
tionContextImpl.java:1014)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRoot
ElementHook(Unknown
Following debug shows that there's some sort of handshake going on...
-Djavax.net.debug=ssl,handshake,data,trustmanager
here is portion
Thread-0, READ: SSL v3.1 Application Data, length = 205 Plaintext after
DECRYPTION: len = 205
0000: 3C 68 74 6D 6C 3E 3C 68 65 61 64 3E 3C 74 69 74 <html><head><tit
0010: 6C 65 3E 52 65 64 69 72 65 63 74 69 6F 6E 3C 2F le>Redirection</
0020: 74 69 74 6C 65 3E 3C 4D 45 54 41 20 48 54 54 50 title><META HTTP
0030: 2D 45 51 55 49 56 3D 52 45 46 52 45 53 48 20 43 -EQUIV=REFRESH C
0040: 4F 4E 54 45 4E 54 3D 30 3B 75 72 6C 3D 68 74 74 ONTENT=0;url=htt
0050: 70 73 3A 2F 2F 74 6F 6D 63 61 74 64 65 76 2E 67 ps://tomcatdev.s
0060: 73 61 6D 2E 67 73 2E 63 6F 6D 2F 66 64 61 78 69 sam.xs.com/fdaxi
0070: 73 2F 73 65 72 76 6C 65 74 2F 41 78 69 73 53 65 s/servlet/AxisSe
0080: 72 76 6C 65 74 3E 3C 4D 45 54 41 20 48 54 54 50 rvlet><META HTTP
0090: 2D 45 51 55 49 56 3D 50 72 61 67 6D 61 20 43 4F -EQUIV=Pragma CO
00A0: 4E 54 45 4E 54 3D 6E 6F 2D 63 61 63 68 65 3E 3C NTENT=no-cache><
00B0: 2F 68 65 61 64 3E 3C 2F 68 74 6D 6C 3E 12 19 47 /head></html>..G
00C0: E6 79 6C 93 F1 E7 DC CA 70 26 BE 1E 23 .yl.....p&..#
Thread-0, SEND SSL v3.1 ALERT: warning, description = close_notify
Plaintext before ENCRYPTION: len = 18
0000: 01 00 D7 6D 0D F1 41 07 D2 C6 F2 B4 2F 3F B9 84 ...m..A...../?..
0010: D6 90 ..
Thread-0, WRITE: SSL v3.1 Alert, length = 18
This debug output shows that somehow Apache is correctly handling SSL
connection and redirecting its request to tomcat...
Has anybody worked with a simiar setup?
Would I need do some setup on Tomcat?
any poninters will be appreciated...
Thanks
Lee
