HLS Public Proxy

Proxy HLS manifests and media segments, rewrite child URLs automatically, test everything directly from this page, and deploy it behind HAProxy for load balancing.

Manifest rewriting Segment passthrough Base64 URL support Custom referer Known origins CORS-friendly HAProxy-ready

Current Proxy Base

URL Builder

Target upstream URL preferred_referer known_origins Input mode

This page automatically uses the current page origin as the proxy base.

Route Summary

GET /

Landing page / docs / quick test UI

GET /health

Returns runtime status and cache counters

GET /proxy/manifest

Fetches an upstream manifest and rewrites child URLs

GET /proxy/segment

Fetches and streams segments or related assets

url=

Normal URL-encoded upstream URL

Base64-encoded upstream URL

preferred_referer=

Overrides the referer sent upstream

known_origins=

One or more trusted origins used for referer handling

Generated Proxy URLs

Manifest URL Segment URL

Included Example

This page includes the exact example you requested.

How It Works

/proxy/manifest

Fetches the upstream playlist, validates it, rewrites child URLs, and returns the rewritten result.

/proxy/segment

Fetches and streams media segments or related assets back to the client.

preferred_referer

Used when the upstream expects a specific referer to allow access.

known_origins

Used to decide when the proxy should apply the preferred referer logic to upstream requests.

Base64 mode

Useful for long URLs or when combining extra query parameters.

HAProxy / load balancing

Works well behind HAProxy or similar reverse proxies, so multiple proxy instances can be balanced behind one public entrypoint.

Notes

/proxy/manifest supports both url= and u=.
/proxy/segment supports both url= and u=.
If both url and u are present, url should be treated as the primary input.
known_origins may be repeated multiple times in the final URL.
preferred_referer should be URL-encoded in the query string.
u should contain the Base64 version of the raw target URL.
HAProxy can be placed in front of one or more proxy instances for load balancing and a single public endpoint.