845e0287c0
SRS forward feature only supports plain RTMP protocol, not RTMPS (RTMP over SSL/TLS). This is by design - SRS SSL is server-side only (accepting connections), not client-side (initiating connections). The forward feature uses SrsSimpleRtmpClient which has no SSL handshake or encryption capabilities for outgoing connections. Changes: 1. Add RTMPS URL detection in SrsForwarder::initialize() 2. Return ERROR_NOT_SUPPORTED error when RTMPS destination is detected 3. Add unit test to verify RTMPS URLs are properly rejected 4. Add FAQ section to .augment-guidelines explaining the limitation For users who need to forward to RTMPS destinations (e.g., AWS IVS), the recommended solution is to use FFmpeg with SRS HTTP Hooks: - on_publish event: Automatically start FFmpeg to relay stream to RTMPS destination - on_unpublish event: Automatically stop FFmpeg process when stream ends This provides a fully automated, production-ready RTMPS relay solution without adding complexity to SRS core. Related: #4536 --------- Co-authored-by: OSSRS-AI <winlinam@gmail.com> |
||
|---|---|---|
| .. | ||
| Architecture.md | ||
| CHANGELOG.md | ||
| Dockers.md | ||
| Features.md | ||
| ffmpeg-logo.png | ||
| ffmpeg-min.png | ||
| PERFORMANCE.md | ||
| README.md | ||
| readme.txt | ||
| Resources.md | ||
| source.200kbps.768x320.flv | ||
| source.flv | ||
| srs-logo.ico | ||
| srs-logo.png | ||
