Bug #2414
closedconfigured lighttpd.conf to proxy to a server on https (port 443):not working
Description
Case A:
I configured my lighttpd.conf file(in my source 'a.b.c.d' system) to proxy to server(p.q.r.s) on port 80. When i type ip address 'a.b.c.d' in url then i can see the proxy opening (of p.q.r.s)..means i am able to see the contents of p.q.r.s on a.b.c.d.
a.b.c.d and p.q.r.s are valid ip address. I have attached the lighttpd.conf file with which this part is working.
Case B:
I configured my lighttpd.conf file(in my source 'a.b.c.d' system) to proxy to server(p.q.r.s) on port 443. When i type ip address 'a.b.c.d' in url then i cannot see any thing opening means the page is blank.
only the change made in the attached lighttpd.conf for this part is changing the port no to 443, as below:
proxy.server = ( "" =>
("localhost" =>
(
"host" => "p.q.r.s",
"port" => 443
)
)
)
I could see from my firebug debugger that the request is going from a.b.c.d to p.q.r.s but there is no response coming back.
When i saw the log on p.q.r.s then it is showing like this..
2000-01-02 04:19:42: (log.c.166) server started
2000-01-02 04:19:42: (server.c.961) WARNING: unknown config-key: webdav.activate (ignored)
2000-01-02 04:19:42: (server.c.961) WARNING: unknown config-key: accesslog.filename (ignored)
2000-01-02 04:19:42: (connections.c.299) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
2000-01-02 04:19:43: (connections.c.299) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
2000-01-02 04:19:46: (connections.c.299) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
2000-01-02 04:19:47: (connections.c.299) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
Note: The same server is working on port 80 but not for port 443.
version of lighttpd:
lighttpd/1.4.28 (ssl) - a light and fast webserver
Build-Date: Mar 22 2012 19:38:03
Is there any settings missed that needs to be done for supporting https(:443)?
Files
Updated by stbuehler about 13 years ago
- Status changed from New to Invalid
- Priority changed from Urgent to Normal
- Target version deleted (
1.4.x)
mod_proxy never supported https. and leave priority settings to developers - a bug is not important just because you think you are.
Updated by anil_pace about 13 years ago
sorry for setting the priority..my fault.
so shall i take it for granted that lighttpd's mod_proxy never supported proxy to ip addresses via port 443? If so, can u suggest me any other light weight server (meant for embedded projects) which can help in this regard.
Updated by stbuehler about 13 years ago
the port is not the problem - the protocol (https) is. you could use simple port forwarding, haproxy for tcp balancing, mod_proxy/stunnel combinations, ...
Also available in: Atom