Skip to content

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

@winlinvip

Description

@winlinvip

The SRS 4.0 HTTP API and Stream listen at different ports, so we must use a HTTP proxy if listen at a single HTTP or HTTPS port. Note that SRS 5.0 supports HTTP API and Stream listen at the same port, such as 8080.

Translation: Currently, the HTTP API and Stream design of SRS 4.0 are separate in order to support API listening on a separate port. However, in simple scenarios, it is inconvenient to use as it requires relying on an external HTTP proxy to combine the API and Stream on a single port.

Note: SRS 5.0 supports using the same port, such as 8080, for both HTTP API and Stream transmission, eliminating the need for a reverse proxy.

You could also use the default self-signed SSL certs, please search thisisunsafe from Wiki.

Ports

SRS 4.0 HTTP API ports:

  • 1985 HTTP API
  • 1990 HTTPS API

SRS 4.0 HTTP Stream ports:

  • 8080 HTTP Stream
  • 8088 HTTPS Stream

SRS 5.0 + HTTP API and Stream ports:

  • 8080 HTTP API and Stream
  • 8088 HTTPS API and Stream

Note: You can config http_api.listen to the same as http_server.listen, such as 8080.

Paths

Nginx Proxy

Caddy Proxy

Nodejs KOA Proxy

HTTPX Proxy

TRANS_BY_GPT3

Metadata

Metadata

Assignees

Labels

EnhancementImprovement or enhancement.FeatureIt's a new feature.TransByAITranslated by AI/GPT.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions