catalyst-node: add redirects for other protocols
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
Minimally we need `/cmaf/` alongside `/hls/`, but ideally we'd have a few more... here's a full list taken from the Mist `embed` page:
```
http://localhost:8080/stream%2bfoo.sdp
ws://localhost:8080/stream%2bfoo.mp4
http://localhost:8080/hls/stream%2bfoo/index.m3u8
http://localhost:8080/stream%2bfoo.mp4
http://localhost:8080/stream%2bfoo.webm
http://localhost:8081/hls/stream%2bfoo/index.m3u8
http://localhost:8080/cmaf/stream%2bfoo/Manifest
http://localhost:8080/cmaf/stream%2bfoo/index.m3u8
http://localhost:8080/cmaf/stream%2bfoo/index.mpd
rtmp://localhost/play/stream%2bfoo
http://localhost:8080/dynamic/stream%2bfoo/manifest.f4m
http://localhost:8080/stream%2bfoo.flv
rtsp://localhost:5554/stream%2bfoo
http://localhost:8080/stream%2bfoo.ts
http://localhost:8080/stream%2bfoo.aac
```
Okay, we don't want quite all of those...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing /hls/ redirect handling in catalyst-node and compare it with the requested /cmaf/ paths listed in the issue. Confirm which additional protocols are in scope with the maintainers, then verify that /cmaf/ and the agreed redirects resolve correctly for the listed stream URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- audio-video-rtc, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100