node-tutorial | For a current sample , see https | Learning library

First, you should make sure to understand the technical difference between what is called "progressive donwloading" a video file with the tag, vs. a real streaming solution that uses the HLS or DASH streaming protocols and "adaptive streaming". There are a lot of resources out there that explain the differences between the two and the customer experiences.

Basically, progressive download will involve a long buffering period for customers on poor networks, and won't be as fast or smooth of a playback experience if network conditions change (like on a cellular network for example.)

You can get the progressive download URL easily by just creating a SAS locator on the MP4 (make it public) in the storage account container, or you can deliver it through the Streaming Locator as well, if you set the streaming policy name to : 'Predefined_DownloadAndClearStreaming'. That will allow you to list the HLS, DASH, and SAS (progressive download) paths. You can also see this easier in the AMSE tool. See this for details on the built-in policy types ( you can also define custom policy types for streaming.) https://docs.microsoft.com/en-us/rest/api/media/streaming-locators/create

You are calling res.end() twice from your request handler when you get either the / or /about requests. You can only call it once.

You end up calling res.end() more than once because when your request matches either / or /about, you call res.end() for those specific pages and then you have another res.end() at the end of the function that also executes.

To fix it, change to this:

Just a suggestion: have you tried resolving the problematic path before passing it to webpack? Something along the lines: path.resolve(__dirname, './src/client') will convert the path from relative to absolute and often times it helps to quiet various loaders.