SRS supports several applications over HTTP.

• HTTP-API: Listens on port 1985 and provides API services.

  Issue: No support for authentication. Authentication is required before proxying to HTTP-API. Callback authentication can also be supported. API: Secure HTTP API for Authentication. Port 1985 does not have any security authentication. #1640
  Issue: No support for HTTPS. Nginx support for HTTPS is required to proxy to SRS. It would be more convenient if SRS supports HTTPS. SSL or HTTPS in port 8080 for HLS #1533

• HTTP-FLV: Listens on port 8080 and provides FLV streaming services.

  Issue: No support for HTTPS. Nginx support for HTTPS is required to proxy to SRS. It would be more convenient if SRS supports HTTPS. SSL or HTTPS in port 8080 for HLS #1533

• HLS: Listens on port 8080 or shares slices with Nginx to provide HLS streaming services.

  Issue: No statistics for HLS clients, unlike RTMP/FLV. It would be more convenient if SRS supports this. In the client statistics interface call, the HLS client was not counted. #1655
  Issue: No authentication for HLS, unlike RTMP/FLV. It would be more convenient if SRS supports this. Does SRS3.0 support authentication for HTTP-HLS requests? #1487
  Issue: No support for HTTPS. Nginx support for HTTPS is required to proxy to SRS. It would be more convenient if SRS supports HTTPS. SSL or HTTPS in port 8080 for HLS #1533

• Using Nginx or Caddy as a proxy to provide unified HTTP/HTTPS services. Refer to HTTP/HTTPS: Reuse or merge port for API and Stream to avoid HTTP Proxy, to avoid proxy, it is recommended to reuse the port. #2881.

If SRS4 or SRS5 enhance the capabilities of HTTP streaming services, it would be more convenient to use and provide stronger consistency.

TRANS_BY_GPT3