don't force SSL and / or update SSLv3 to TLS1.2 at least

[gaelbillard]

The current image send a 301 - permanent moving to https wheh trying to connect with http but the SSL ask for SSLv3 which is no more available. When used bahind a front like nginx / apache, SSL is useless. This behavior should be de/activable using parameter (either docker command line or docker-compose env for example. I tried to locate where to modify but didn't know ruby :( I didn't found how to specify development instead of production by login into running container either

[erhhung]

Any update on this? Requiring HTTPS with SSLv3 for a local deployment makes it completely unusable.

curl -vkL http://localhost:5050/

* Uses proxy env variable no_proxy == 'localhost,::1,127.0.0.1'
*   Trying 127.0.0.1:5050...
* Connected to localhost (127.0.0.1) port 5050 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* error:1408F10B:SSL routines:ssl3_get_record:wrong version number
* Closing connection 0

curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number