There is a work-around:

Use nginx or go-oryx/httpx-static to covert HTTP to HTTPS, or HTTPS直播实战，搞定HTTPS-HLS和HTTPS-FLV 。

Whatever, SRS will support HTTPS client and server inside.

HTTPS Client protocol:

• Wiki: SRS Callback for HTTPS Server.

HTTP callback support HTTPS server, for example, conf/https.hooks.callback.conf :

vhost __defaultVhost__ {
    http_hooks {
        enabled         on;
        on_connect      https://127.0.0.1:443/api/v1/clients;
    }
}

The log of SRS, for https-client:

[2020-11-03 15:47:58.645][Trace][4715][h6r1ehdh] RTMP client ip=127.0.0.1:61658, fd=10
[2020-11-03 15:52:35.021][Trace][5547][2m457139] https: connected to https://127.0.0.1:443, cost=6ms
[2020-11-03 15:47:58.658][Trace][4715][h6r1ehdh] http: on_connect ok, client_id=h6r1ehdh, 
url=https://127.0.0.1:443/api/v1/clients, request={"action":"on_connect", 
"client_id":"h6r1ehdh","ip":"127.0.0.1","vhost":"__defaultVhost__","app":"live",
"tcUrl":"rtmp://127.0.0.1:1935/live","pageUrl":""}, 
response={"code": 0, "data": null}

Note: The wireshark capture file for HTTPS client: https-client.pcapng.zip

Note: Refer to OpenSSL example using memory BIO with non-blocking socket IO .

HTTPS API server protocol:

• Wiki: SRS Supports HTTPS API .

Config for HTTPS API, for example, conf/https.rtc.conf :

http_api {
    enabled         on;
    listen          1985;
    # For https_api or HTTPS API.
    https {
        # Whether enable HTTPS API.
        # default: off
        enabled on;
        # The listen endpoint for HTTPS API.
        # default: 1990
        listen 1990;
        # The SSL private key file, generated by:
        #       openssl genrsa -out server.key 2048
        # default: ./conf/server.key
        key ./conf/server.key;
        # The SSL public cert file, generated by:
        #       openssl req -new -x509 -key server.key -out server.crt -days 3650 -subj "/C=CN/ST=Beijing/L=Beijing/O=Me/OU=Me/CN=ossrs.net"
        # default: ./conf/server.crt
        cert ./conf/server.crt;
    }
}

Open in Chrome:

• HTTPS: https://127.0.0.1:1990/api/v1/versions
• HTTP: http://127.0.0.1:1985/api/v1/versions

The SRS logs:

[2020-11-06 17:14:10.700][Trace][21509][551p56t8] https: api server done, use key 
./conf/server.key and cert ./conf/server.crt, cost=5ms
[2020-11-06 17:14:10.700][Trace][21509][551p56t8] HTTP #0 127.0.0.1:62381 GET 
https://127.0.0.1:1990/api/v1/versions, content-length=-1

# For self-sign certificate, there is always a error:
[2020-11-06 17:17:35.939][Error][21509][551p56t8][0] serve error code=4042 : start : handshake : handshake r0=-1, r1=1
thread [21509][551p56t8]: do_cycle() [src/app/srs_app_http_conn.cpp:170][errno=0]
thread [21509][551p56t8]: on_start() [src/app/srs_app_http_api.cpp:1710][errno=0]
thread [21509][551p56t8]: handshake() [src/app/srs_app_conn.cpp:624][errno=0]

Note: Capture files https-server-port-1443.pcapng.zip , https-server.pcapng.zip

Note: Refer to OpenSSL example using memory BIO with non-blocking socket IO .

值得好好做，打好HTTP基础。

HTTP-API相关的Issue，都汇总到这个issue更新：

• http api 未统计webrtc 分发流个数(即client个数) http api 未统计webrtc 分发流个数(即client个数) #2290
• SRS4.0版本-http接口返回结果异常问题 https://github.com/ossrs/srs/issues/2231
• srs rtmp推流 webrtc观看 ，如何获取webrtc客户端信息，控制台只能获取推流信息 WebRTC: 提供类似chrome://webrtc-internals的统计信息 #2149
• 2.0.243 HTTP API未统计播放HLS的客户端 2.0.243 HTTP API未统计播放HLS的客户端 #996
• APPLICATION: 当使用http-flv播放时，调用srs http api查看流量统计不对，客户端连接数是对的 APPLICATION: 当使用http-flv播放时，调用srs http api查看流量统计不对，客户端连接数是对的 #863

期待SRS4能支持HLS的clients统计和HLS的on_play/on_stop回调