Actions
Bug #7167
closed--https-listen command line option does not invoke 'create SSL context'
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/04/2019
Due date:
% Done:
0%
Estimated time:
Description
I think I have narrowed this down to line 207 in src/http/Server.C:
if (!config_.httpsAddress().empty() && config_.parentPort() == -1) {
This forces the use of:
--https-address
--https-port
rather than the newer
--https-listen
After changing the command line arguments to match, the 'no shared cipher' message goes away and successful ssl connections are made.
No SSL context is being created with ---https-listen option.
Updated by Roel Standaert over 4 years ago
- Status changed from New to Resolved
Looks like that was indeed an oversight, we should init the ssl_context
when --https-listen
is used, too. I pushed a fix to 4.1-release
and master
.
Updated by Roel Standaert about 4 years ago
- Status changed from Resolved to Closed
Fix released in 4.1.1
Actions