Bug #1001
closedProxy Secure connections Error : (connections.c.538) connection closed: write failed on fd 8
Description
Hello,
We have a few lighttpd servers running proxies and images. We love it.
However we have come across an issue with secure connections.
ssl works.
../sbin/lighttpdssl -v
lighttpd-1.4.11 (ssl) - a light and fast webserver
Build-Date: Jan 26 2007 13:48:49
I can get into a dir securely as a test.
I can get to the proxy location securely just fine as well.
I can proxy to a certain port just fine. (ie port 80)
When I change this to point to port 443 I get the following error :
(connections.c.538) connection closed: write failed on fd 8
lighttpd conf:ips & domains have been changed:
- SSL engine
server.name = "cc.asdf.net"
ssl.engine = "enable"
ssl.ca-file = "/usr/local/lighttpdssl/certs/cc.asdf.net.crt"
ssl.pemfile = "/usr/local/lighttpdssl/certs/cc.asdf.net.pem"
$SERVER[[socket]] == "204.13.160.129:443" {#server.document-root = "/var/www/html/test"
proxy.server = ( "" => (
("host" => "208.97.134.217","port"=> 443)
)
)
}
Any ideas?
Updated by kdlarg about 18 years ago
Sorry let me add more info from the error log:
2007-01-29 12:00:51: (request.c.293) fd: 8 request-len: 438
GET / HTTP/1.1
Host: cc.asdf.net
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060501 Fedora/1.7.13-1.1.fc4
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cache-Control: max-age=0
2007-01-29 12:00:51: (response.c.196) -- splitting Request-URI
2007-01-29 12:00:51: (response.c.197) Request-URI : /
2007-01-29 12:00:51: (response.c.198) URI-scheme : https
2007-01-29 12:00:51: (response.c.199) URI-authority: cc.asdf.net
2007-01-29 12:00:51: (response.c.200) URI-path : /
2007-01-29 12:00:51: (response.c.201) URI-query :
2007-01-29 12:00:51: (response.c.251) -- sanatising URI
2007-01-29 12:00:51: (response.c.252) URI-path : /
2007-01-29 12:00:51: (response.c.360) -- before doc_root
2007-01-29 12:00:51: (response.c.361) Doc-Root : /var/www/html
2007-01-29 12:00:51: (response.c.362) Rel-Path : /
2007-01-29 12:00:51: (response.c.363) Path :
2007-01-29 12:00:51: (response.c.411) -- after doc_root
2007-01-29 12:00:51: (response.c.412) Doc-Root : /var/www/html
2007-01-29 12:00:51: (response.c.413) Rel-Path : /
2007-01-29 12:00:51: (response.c.414) Path : /var/www/html/
2007-01-29 12:00:51: (response.c.431) -- logical -> physical
2007-01-29 12:00:51: (response.c.432) Doc-Root : /var/www/html
2007-01-29 12:00:51: (response.c.433) Rel-Path : /
2007-01-29 12:00:51: (response.c.434) Path : /var/www/html/
2007-01-29 12:00:51: (response.c.111) Response-Header:
HTTP/1.1 200 OK
Content-Length: 0
Date: Mon, 29 Jan 2007 17:00:51 GMT
Server: lighttpd/1.4.11
2007-01-29 12:00:51: (network_openssl.c.115) SSL (error): 5 0 0 Success
2007-01-29 12:00:51: (connections.c.538) connection closed: write failed on fd 8
Updated by darix about 18 years ago
the http proxy module doesnt speak https. your proxy backend needs to speak plain http.
does the port 443 in your proxy block imply the server is running https?
Updated by kdlarg about 18 years ago
Replying to darix:
the http proxy module doesnt speak https. your proxy backend needs to speak plain http.
does the port 443 in your proxy block imply the server is running https?
yes both servers have certs and run https.
Updated by stbuehler almost 17 years ago
- Status changed from New to Fixed
- Resolution set to invalid
mod_proxy doesn't speak https, and this is not a bug.
Also available in: Atom