After modifying SOAP to open an SSL socket over a tunnel socket on our proxy server,
such as in jsse
tunneling example (see thread Apache SOAP V2.2 client using SSL behind a proxy doesn't
work ), I am
still getting an error trying to send a message to IBM test UDDI registry, but it
looks to me like an
error from the IBM web site itself. Below are debugs printed from my code, which
shows that the
handshake is apparently successful, and shows the header and body that is actually
being sent (using
uddi4j SaveBusinessExample), and finally shows the response (403 error) that is being
returned. If I
modify SaveBusinesExample to use Microsoft test server, it still fails, but I get a
405 error back.
Does anyone have any advice about what is happening here?
Bethany
-----------------
Attempting handshake: CONNECT www-3.ibm.com:443 HTTP/1.0
User-Agent: Java1.2.2
Handshake completed: HTTP/1.0 200 Connection established
overlaying socket to www-3.ibm.com:443
Header is POST https://www-3.ibm.com/services/uddi/testregistry/protect/publishapi
HTTP/1.0
Host: www-3.ibm.com
Content-Type: text/xml; charset=utf-8
Content-Length: 366
SOAPAction: ""
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<get_authToken cred="scrubbed" generic="1.0" userID="scrubbed"
xmlns="urn:uddi-org:api"/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response: HTTP/1.1 403 Forbidden by rule.