Hmmm,
I guess I'm already one step closer :).
Do I also need to define the transportreceiver for HTTPS? I've read
something about configure the services.xml with the following stuff:
<transports>
<transport>https</transport>
</transports>
So that you only have the https transport. But if I do this, he
complains that HTTPS is not defined as transport.
If you uncomment the section in axis2.xml
<transportReceiver name="https"
class="org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener">
<parameter name="port" locked="false">7002</parameter>
<parameter name="non-blocking" locked="false">true</parameter>
<parameter name="keystore" locked="false">
<KeyStore>
<Location>identity.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
<KeyPassword>password</KeyPassword>
</KeyStore>
</parameter>
<parameter name="truststore" locked="false">
<TrustStore>
<Location>trust.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
</TrustStore>
</parameter>-->
<!--<parameter name="SSLVerifyClient">require</parameter>
supports optional|require or defaults to none -->
</transportReceiver>
He complains that he doesn't find the class:
org/apache/http/impl/nio/reactor/SSLIOSessionHandler
Can someone help?
Kind regards
Jan Verstuyft
2008/7/8 Jan Verstuyft <[EMAIL PROTECTED]>:
> Hi,
>
> we had a default configuration for our axis2 webservices and now we
> want to put this on a HTTPS configuration. The intention is also to
> block the http request.
>
> Because we've found some settings in the axis2.xml:
> <transportSender name="http"
>
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> <parameter name="PROTOCOL">HTTP/1.1</parameter>
> </transportSender>
>
> <transportSender name="https"
>
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> <parameter name="PROTOCOL">HTTP/1.1</parameter>
> </transportSender>
>
> We've thought that we don't need to change anything on the axis2
> configuration.
> But, if our system administrator configure the webserver to only
> accept the HTTPS, we receive a timeout for the request for the WSDL.
> Only after 45 seconds, the requested wsdl is shown. And even then, in
> the wsdl, the default paths are still http://...
>
>
> What do we need to configure so that HTTPS will works?
>
> Kind regards
>
> Jan Verstuyft
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
