What it is

httpx-static is a HTTP/HTTPS API proxy that ships as one component inside go-oryx, a collection of isolated processes maintained under the SRS (Simple Realtime Server) project. The repository describes oryx as a group of separate processes, and httpx-static is one of them: a static file server that also fronts API traffic over both HTTP and HTTPS. The project is written in Go and released under the MIT license, and it belongs to the SRS ecosystem, the media server family whose homepage is hosted at the ossrs/srs repository.

The concrete problem it solves is the separation of concerns inside a streaming deployment. A live streaming stack has to serve static assets and proxy API requests while other processes handle ingestion and delivery, and httpx-static exists so that those serving duties live in their own process rather than being folded into the media server itself. Its topic list places it squarely in the live media domain, alongside cdn, cluster, hls, http-flv, http-streaming, live-streaming, media-server, rtmp, rtmp-server, and srs, which describes the environment it is built to sit in.

Key capabilities

• Serves static files over HTTP.
• Serves static files over HTTPS.
• Acts as an API proxy.
• Runs as an isolated process within the go-oryx process group.
• Targets the live streaming context defined by its topics: hls, http-flv, and http-streaming.
• Built in Go, so it compiles to a single binary.
• Distributed under the MIT license.

Who uses it and how

• Operators running SRS-based live streaming deployments who need static asset serving kept out of the media server process.
• Teams that need an API proxy in front of backend services while the same process serves files.
• Deployments that already run the oryx group of isolated processes and add httpx-static as one member.
• Sites serving HLS or HTTP-FLV playback assets where static delivery and proxying are handled by one small service.
• Setups using RTMP or RTMP server ingestion alongside HTTP-based delivery, as reflected in the topic list.

Getting started

The README excerpt does not document install commands, Docker image names, package managers, or a hosted option; it identifies httpx-static only as an HTTP/HTTPS static server with API proxy inside the go-oryx process group. Since the project is written in Go, the practical starting point is the ossrs/go-oryx repository itself.

When to use it — and when not to

No paid products are listed as alternatives, so the comparison sits between running httpx-static and running a general-purpose web server or reverse proxy for the same static-plus-proxy duty. A self-hoster must operate the surrounding SRS and go-oryx processes, since httpx-static is one isolated process in that group rather than a standalone product. The evident weakness is documentation: the README excerpt gives no install, configuration, or deployment instructions, so the operator must work from the repository.