Bug#773845: Acknowledgement (curl: Got empty reply from server error on some HTTPS websites)

2015-01-30 Thread Alessandro Ghedini
On Sun, Jan 04, 2015 at 11:52:11PM +0100, Jean Baptiste Favre wrote: Problem has been solved changing nginx configuration. It seems that following option was responsible of the empty error: ssl_session_cache shared:SSL:5m; Sorry for the delay (again...), I added that configuration option to my

Bug#773845: Acknowledgement (curl: Got empty reply from server error on some HTTPS websites)

2015-01-07 Thread Jean Baptiste Favre
Hello, Thanks for your acknowledgement. I made some further search and found what looks like the root cause: http://trac.nginx.org/nginx/ticket/235 It's a nginx issue, but could help to reproduce and investigate curl's one. Regards, Jean Baptiste On 07/01/2015 22:52, Alessandro Ghedini wrote:

Bug#773845: Acknowledgement (curl: Got empty reply from server error on some HTTPS websites)

2015-01-07 Thread Alessandro Ghedini
On Sun, Jan 04, 2015 at 11:52:11PM +0100, Jean Baptiste Favre wrote: Problem has been solved changing nginx configuration. It seems that following option was responsible of the empty error: ssl_session_cache shared:SSL:5m; Therefore, I downgrade bug severity. But, I prefer to keep it opened

Bug#773845: Acknowledgement (curl: Got empty reply from server error on some HTTPS websites)

2015-01-04 Thread Jean Baptiste Favre
Problem has been solved changing nginx configuration. It seems that following option was responsible of the empty error: ssl_session_cache shared:SSL:5m; Therefore, I downgrade bug severity. But, I prefer to keep it opened since: - openssl s_client calls work - wget call work - I don't see the