Should detect double-slash in RTMP ingest URL
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**What's the problem? (required)**
Sometimes the encoding software doesn't do a good job creating the RTMP ingest URL (for example, Wirecast). Especially when the user is copy/pasting the URL, it's easy to end up with something like `rtmp://mdw-rtmp.livepeer.com/live//{stream-key}`. In this case, our API doesn't accept the stream.
**What's the current behavior? (required)**
Our API should recognize this case and still accept the stream.
Contributor guide
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
No implementation file or test is named. Start by locating the API's RTMP ingest URL validation and its existing tests; reproduce the double-slash form, then verify that the stream is accepted without changing other URL handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100