Two edge-cluster regressions surfaced when validating an RTMP origin/edge setup. Each is a small, surgical fix in its own commit. - **HTTP-FLV play on edge always 404'd.** `SrsHttpStreamServer::assemble()` registered the dynamic matcher only when the mux cast was `NULL` (inverted guard), so the matcher was never wired up. On edge the FLV mount is created lazily by the dynamic matcher, so every HTTP-FLV client got 404. Invert the guard to register when the mux is valid, mirroring the destructor. (`trunk/src/app/srs_app_http_stream.cpp`) - **RTMP players that join an edge stream after the first player fail to decode.** After v7.0.94 (#4513) stopped creating `SrsOriginHub` on edge, the `hub_active` gate in `SrsLiveSource::consumer_dumps()` always evaluated false on edge. That gate guards the dump of cached `onMetaData` + AVC sequence header + AAC sequence header + GOP cache to a new consumer. Result: the first player attaches before the edge-pull starts and gets headers via the live fan-out, but every subsequent player gets coded payload with no codec config and ffmpeg aborts with `dimensions not set` / `Could not write header`. Fall back to the meta cache state when `hub_` is `NULL`, so the dump path runs once the edge-pull has populated the cache. (`trunk/src/app/srs_app_rtmp_source.cpp`) --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
20 lines
469 B
Plaintext
20 lines
469 B
Plaintext
|
|
# Upstream origin for the proxy+edge E2E test (skills/srs-develop).
|
|
# Not registered with the proxy; the edge in front of it is. The edge pulls
|
|
# from this origin on play and pushes publishes here on publish.
|
|
|
|
max_connections 1000;
|
|
pid objs/origin-for-edge.pid;
|
|
daemon off;
|
|
srs_log_tank console;
|
|
|
|
rtmp {
|
|
listen 19360;
|
|
}
|
|
http_api {
|
|
enabled on;
|
|
listen 19860;
|
|
}
|
|
vhost __defaultVhost__ {
|
|
}
|