404 errors on transport stream files when using edge server

[LucasMallmann]

Description

When setting up the project and running locally, accessing the URL http://localhost:8080/golive/index.m3u8 allows the content to be watched as expected. However, when switching the URL to http://localhost:8081/golive/index.m3u8, which routes the request through the edge server (before reaching the origin), 404 errors occur for the transport stream (.ts) files.

• Manifest File Behavior: The manifest file (index.m3u8) is correctly served by the edge server, thanks to a specific rule.
• Issue: Although the manifest is accessible, it references .ts files that are not being found by the server, resulting in 404 errors for these files.

How to encounter/reproduce bug

1. Run the project locally
2. Access the content via http://localhost:8080/golive/index.m3u8 (origin server) – content plays successfully.
3. Change the URL to http://localhost:8081/golive/index.m3u8 (edge server first) – manifest is served, but 404 errors occur for .ts files.

[mauricioabreu]

Fixed via 9a5f819

Do you mind checking again if it is working as expected?

Thank you for reporting this error - fixing it was easy due to all the details you have given.

[LucasMallmann]

@mauricioabreu it worked just fine! I checked here and now I can watch the stream via the edge server (http://localhost:8081/golive/index.m3u8).

Thank you for the support.