From f72ffc1ff9743f89f044e97d573cb3719c5eeeaf Mon Sep 17 00:00:00 2001
From: Alexander Traud <pabstraud@compuserve.com>
Date: Mon, 20 Jun 2016 15:05:09 +0200
Subject: [PATCH] http: leverage 'bindaddr' for TLS in http.conf
The internal HTTP/WebSocket server supports both TCP and TLS, which can be
activated separately via the file http.conf. The source code intends to re-use
the TCP parameter 'bindaddr' for TLS, even if 'tlsbindaddr' is not specified
explicitly. This did not work because of a typo. This change resolves this typo.
ASTERISK-26126 #close
Change-Id: I5efb0409ae12044dfb3495b6b97b6d40a8c9c51f
---
main/http.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/main/http.c b/main/http.c
index a8362829ef..bc23e6e563 100644
--- a/main/http.c
+++ b/main/http.c
@@ -2220,7 +2220,7 @@ static int __ast_http_load(int reload)
* the non-TLS bindaddress here.
*/
if (ast_sockaddr_isnull(&https_desc.local_address) && http_desc.accept_fd != -1) {
- ast_sockaddr_copy(&https_desc.local_address, &https_desc.local_address);
+ ast_sockaddr_copy(&https_desc.local_address, &http_desc.local_address);
/* Of course, we can't use the same port though.
* Since no bind address was specified, we just use the
* default TLS port
--
GitLab