[Chilli] SSL on Chili

Fernando Dutra Fagundes Macedo fmacedo at cpd.ufrgs.br
Thu Nov 19 16:25:15 UTC 2009

I think that I wasn't enough clear describing the problem in the last
message. I'll try to explain this issue with more details:

The problem happens When coova chilli is configured to work with ssl and
a client tries to connect to a http server (port 80). In this
sittuation, coova redirects the connection to port 3990 which is working
with ssl. Although, the client have made a request to connect to a http
server, not https. So, the ssl negotiation fails, the client didn't
connect properly and presents a blank page to the user.

We have been trying to solve this issue but we hadn't any good ideas
until now. The best solution we thought was to redirect the connection
to apache and after do a http redirection from http to https and then
return back the connection to coova.

The scenario now is like this:
1. http request to http://www.abcdefgh.com
2. coova redirects to port 3990 with ssl
3. ssl negotiation fails

And we want coova to work like this:
1. http request to http://www.abcdefgh.com
2. coova redirects to apache port 80
3. apache makes a http to https redirection to coova
4. coova receives https connection on port 3990 and the ssl negotiation

Could someone help us or give us some directions on how to modify the
code to solve this problem?



Fernando Macedo


De: chilli-bounces at coova.org [mailto:chilli-bounces at coova.org] Em nome
de Fernando Dutra Fagundes Macedo
Enviada: quinta-feira, 12 de novembro de 2009 12:51
Para: chilli at coova.org
Assunto: [Chilli] SSL on Chili




When using ssl on chilli, the first page that a user must open must be
HTTPS because chilli will respond only connections over ssl. How can I
accept the two types of redirection (80 and 443) when using ssl?




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20091119/49795539/attachment.htm>

More information about the Chilli mailing list