[Spce-user] SSL for the provisioning interface

Andreas Granig agranig at sipwise.com
Wed Dec 29 08:14:58 EST 2010


Hi,

Double-check that you really use https in your uri scheme when communicating with the provisioning interface.

Andreas



"Robert C. Chandler II" <robert3056519624 at yahoo.com> schrieb:

>I'm receiving the following message when I try to test the provisioning
>
>interface with 
>
>the default CE self-signed SSL certificate (using https and port number
>2443).
> 
> 
>---DATA---
><!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
><html><head>
><title>400 Bad Request</title>
></head><body>
><h1>Bad Request</h1>
><p>Your browser sent a request that this server could not
>understand.<br />
>Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
>Instead use the HTTPS scheme to access this URL, please.<br />
><blockquote>Hint: <a 
>href="https://myserver/"><b>https://myserver/</b></a></blockquote></p>
><hr>
><address>Apache/2.2.9 (Debian) mod_ssl/2.2.9 OpenSSL/0.9.8g
>mod_perl/2.0.4 
>Perl/v5.10.0 Server at myserver Port 443</address>
></body></html>
>
>---END DATA---
>
>Is a certificate signed by a CA required to use the provisioning
>interface via 
>XML-RPC or can I use a 
>
>self-signed certificate?  If a CA signed certificate is required for
>SSL how can 
>I temporarily disable SSL 
>
>while I test the provisioning interface?
>
>
>_______________________________________________
>Spce-user mailing list
>Spce-user at lists.sipwise.com
>http://lists.sipwise.com/listinfo/spce-user





More information about the Spce-user mailing list