| Summary: | ASTERISK-26126: [patch] leverage 'bindaddr' for TLS in http.conf | ||
| Reporter: | Alexander Traud (traud) | Labels: | |
| Date Opened: | 2016-06-20 08:04:27 | Date Closed: | 2016-06-20 12:05:49 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Core/HTTP |
| Versions: | 11.22.0 13.9.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) secure_websocket.patch | |
| Description: | 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. The attached resolves this typo.
Although looking cosmetic on the first glance, this bug was reported, because {{http.conf.sample}} states {{tlsbindaddr}} would default to {{bindaddr}} – and I lost an hour because of that. This is a regression of [Review Board 986|https://reviewboard.asterisk.org/r/986/] by [~mmichelson]. | ||
| Comments: | |||