Bug #2960
closedLighttpd + SSL + google chrome = ERROR EMPTY RESPONSE (bug in Ubuntu pkgs)
Description
I have a test website setup with lighttpd (ubuntu 18.04 server)
It works with any other browser but chrome gives an empty page if I connect in HTTPS.
This page isn’t working qsd.zibri.org didn’t send any data.
ERR_EMPTY_RESPONSE
The certificates are right.. I really don't know what to do.
The version is: lighttpd/1.4.45 (ssl) (Feb 6 2018 12:41:51)
Updated by Zibri almost 6 years ago
Update: I cloned the git repository and compiled it from sources. and The issue is not there.
So the problem is with the actual version for ubuntu 18.04.
Updated by gstrauss almost 6 years ago
- Subject changed from Lighttpd + SSL + google chrome = ERROR EMPTY RESPONSE to Lighttpd + SSL + google chrome = ERROR EMPTY RESPONSE (bug in Ubuntu pkgs)
- Category deleted (
core) - Status changed from New to Invalid
- Priority changed from Normal to Low
- Target version deleted (
1.4.x)
Update: I cloned the git repository and compiled it from sources. and The issue is not there.
So the problem is with the actual version for ubuntu 18.04.
- This is lighttpd's website, not Ubuntu's. You're posting in the wrong place.
- You're posting a request for help, not a bug. Don't file bug reports to ask questions. ("Has anyone seen this?")
- Don't file bug reports for things that have already been asked and answered on both Ubuntu and lighttpd forums.
https://redmine.lighttpd.net/boards/2/topics/8644
For https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1800605
See #2912. This was fixed in 7a7f4f98 and released in lighttpd 1.4.51 over 8 months ago.
For https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1832295
please note that the poster there already states that lighttpd 1.4.54 works on Ubuntu.
BTW, the latest version of lighttpd is lighttpd 1.4.54, which is nine (9) full releases beyond what you are running. (Whine at your distro of choice for being years out of date. lighttpd 1.4.45 was released Jan 2017, almost 2 1/2 years ago. Way to pay attention, Ubuntu.)
Updated by Zibri almost 6 years ago
1) I didn't write to ask for any help. I am perfectly capable of solving the problem in many ways.
2) I thought you wanted to be informed of this, since google does not give so relevant results on this matter.
3) sorry if I bothered you. Next time I will just keep it to myself.
so long
Updated by gstrauss almost 6 years ago
I am perfectly capable of solving the problem in many ways.
I don't think you should use the word "perfectly". You failed to search lighttpd's website using the search feature (see the Search box on the top right of this page), and you failed to search Ubuntu forums using the search on Ubunutu's site. These are trivial steps you could have taken to find the answer to your question. No expertise required.
Updated by Zibri almost 6 years ago
that's because at first I didn't know it was a lighttpd problem since it worked until a few days ago then after some chrome updates it showed up.
nevermind
Updated by gstrauss almost 6 years ago
It's not a lighttpd problem. It's not a Chrome problem. It's an Ubuntu packaging issue. A major change was made in Ubuntu to upgrade an underlying library (openssl) to a version which added TLS 1.3 support. TLS 1.3 changes behavior. Current Chrome supports TLS 1.3.
https://github.com/openssl/openssl/issues/5721 "TLSv1.3 unexpected InfoCallback after handshake completed"
https://wiki.openssl.org/index.php/TLS1.3 "Renegotiation is not possible in a TLSv1.3 connection"
lighttpd (and other web servers) reject renegotiation by default to protect against https://bugs.launchpad.net/bugs/cve/2009-3555
(link from the Ubuntu bug report https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1800605)
Current versions of lighttpd adjust behavior to handle TLS 1.3 differently from earlier versions of TLS with regards to renegotiations. At the moment, Ubuntu ships a version of lighttpd which is too old to handle TLS 1.3.
Also available in: Atom