Hi kannel's

> a) You want to be able to use HTTP *and* HTTPS to *one* port (i.e.
> 443) for the sendsms HTTP interface.
 No !

> b) You want to have *only* HTTPS for the sendsms HTTP interface, but
> HTTP *and* HTTPS client support for the sms-service groups.
 No !

Ok. Let me explain the scenario a little bit more.

We have one HTTPS webserver and we have one HTTP webserver.
Both servers hold a site with a "send SMS" formular.
If SSL is enabled, only the HTTPS webserver will send the SMS correctly
via SSL tunnel, and the smsbox receives it and sends the message to the
recipient successful. Thats ok, the other HTTP webserver sends the SMS to
the smsbox too, but the smsbox did not treat the request.
Over again the error message...

2002-01-25 09:54:41 [2] ERROR: HTTP: unsuccessfull SSL handshake for client
`195.233.210.4'
2002-01-25 09:55:41 [2] WARNING: SSL: handshake failed: HTTP spoken on HTTPS
port
2002-01-25 09:55:41 [2] WARNING: SSL: OpenSSL: error:1407609C:SSL
routines:SSL23_GET_CLIENT_HELLO:http request
2002-01-25 09:55:41 [2] WARNING: SSL: disconnecting.

Sure, the warning is correct, because it is a HTTP request.

Is it not really possible to configure kannel to handle request from
HTTP and HTTPS servers (client's)?


Thanks in advanced

Bjoern






-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im Auftrag von Stipe Tolj
Gesendet: Freitag, 25. Januar 2002 23:57
An: Bjoern Buettner
Cc: [EMAIL PROTECTED]
Betreff: Re: handshake error with SSL


Bjoern,

while re-reading this thread I think Andreas and I missed what you
meant in your question.

Which one is it:

a) You want to be able to use HTTP *and* HTTPS to *one* port (i.e.
443) for the sendsms HTTP interface.

b) You want to have *only* HTTPS for the sendsms HTTP interface, but
HTTP *and* HTTPS client support for the sms-service groups.

c) You don't care for what the sendsms HTTP interface is used, you
just want to assure you can do HTTP *and* HTTPS for the sms-service
groups (i.e. url = "http://foo"; and url = "https://bar";.

I'm guessing c). So I'll answer to c):

If you compiled in SSL-support then you don't have to "activate" the
HTTPS client support in Kannel. smsbox-port-ssl activates *only* the
SSL-enabling of the HTTP server for the sendsms interface. You can use
"https://"; schemes directly in the sms-service groups.

Stipe

[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are



---------------------------------------------------------
This Mail has been checked for Viruses
Attention: Encrypted mails can NOT be checked!

**

Diese Mail wurde auf Viren geprueft
Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden!
---------------------------------------------------------


Reply via email to