[prev in list] [next in list] [prev in thread] [next in thread]
List: axis-c-dev
Subject: [jira] Created: (AXIS2C-1399) Invalid Transport Protocol, HTTPS
From: "George Sherwood (JIRA)" <jira () apache ! org>
Date: 2009-09-29 21:35:07
Message-ID: 1431005846.1254260107936.JavaMail.jira () brutus
[Download RAW message or body]
Invalid Transport Protocol, HTTPS transport not enabled on Linux
----------------------------------------------------------------
Key: AXIS2C-1399
URL: https://issues.apache.org/jira/browse/AXIS2C-1399
Project: Axis2-C
Issue Type: Bug
Components: transport/http
Affects Versions: 1.6.0
Environment: Red Hat EL 4.7 and Apache2 httpd-2.0.63. Axis2/C is deployed as an Apache2 module.
Reporter: George Sherwood
(From axis-c-user list message "SSL configuration question" 2009-09-27 2:44:52)
I have been using axis2c-src-1.6.0 for a few days with an existing service running \
Red Hat EL 4.7 and Apache2 httpd-2.0.63. Axis2/C is deployed as an Apache2 module. \
The samples and hello work with http transport, but I have not run https successfully \
with axis2 yet. The problem appears to be similar to that reported 2009-05-14 by \
chankm (Kwang Mien), but there does not seem to be a response to that message in the \
archive. Can anyone explain why axis2c is not using https here? Thanks for the help.
George Sherwood
I am using a test system with a self-signed certificate. SSL is working with httpd; \
e.g. https://64.232.245.115/pub/promos.php is accessed as expected from a remote \
browser. However SSL does not appear to be configured correctly for axis2.
Both of the following commands seem to run OK.
./echo http://64.232.245.115/axis2/services/echo
./hello http://64.232.245.115/axis2/services/hello
But the responses for the corresponding https endpoints do not.
./echo https://64.232.245.115:443/axis2/services/echo
yields "echo client invoke FAILED!"
./hello https://64.232.245.115:443/axis2/services/hello
yields "hello client invoke FAILED!"
The echo.log contains the following lines.
[Sat Sep 26 20:01:13 2009] [error] http_client.c(271) Transport protocol is \
unsupported by axis2
[Sat Sep 26 20:01:13 2009] [error] http_client.c(272) Invalid Transport Protocol, \
HTTPS transport not enabled.
[Sat Sep 26 20:01:13 2009] [error] http_client.c(544) client data stream null or \
socket error for host 64.232.245.115 and 443 port
[Sat Sep 26 20:01:13 2009] [error] http_client.c(548) A read attempt(HTTP) for the \
reply without sending the request
[Sat Sep 26 20:01:13 2009] [error] http_sender.c(1381) status_code < 0
[Sat Sep 26 20:01:13 2009] [error] engine.c(179) Transport sender invoke failed
[Sat Sep 26 20:01:13 2009] [error] echo.c(145) Stub invoke FAILED: Error code: 75 :: \
A read attempt(HTTP) for the reply without sending the request
And the hello_client.log contains the following lines.
[Sat Sep 26 20:17:19 2009] [error] http_client.c(271) Transport protocol is \
unsupported by axis2
[Sat Sep 26 20:17:19 2009] [error] http_client.c(272) Invalid Transport Protocol, \
HTTPS transport not enabled.
[Sat Sep 26 20:17:19 2009] [error] http_client.c(544) client data stream null or \
socket error for host 64.232.245.115 and 443 port
[Sat Sep 26 20:17:19 2009] [error] http_client.c(548) A read attempt(HTTP) for the \
reply without sending the request
[Sat Sep 26 20:17:19 2009] [error] http_sender.c(1381) status_code < 0
[Sat Sep 26 20:17:19 2009] [error] engine.c(179) Transport sender invoke failed
[Sat Sep 26 20:17:19 2009] [error] hello.c(94) Stub invoke FAILED: Error code: 75 :: \
A read attempt(HTTP) for the reply without sending the request
Relevant lines from the axis2.xml file are:
<transportReceiver name="https" class="axis2_http_receiver">
<parameter name="port" locked="false">443</parameter>
<parameter name="exposeHeaders" locked="true">false</parameter>
</transportReceiver>
...
<transportSender name="https" class="axis2_http_sender">
<parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
</transportSender>
<parameter name="SERVER_CERT">/usr/local/apache2/conf/ssl.crt/64.232.245.115.crt</ \
parameter>
Both the server module and SSL client were configured with openssl enabled. Details \
are available if needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic