This little script is requesting an OpenLoad embed link, pressing the play button once, which triggers a network request to the video file’s URL. To solve this issue, I wrote a small script which is using Chromium’s Puppeteer tool for creating headless requests using the Chromium browser. OpenLoad is fetching the source video URL after you press play, so it’s not as easy as fetching the video’s source code and parsing the link, because it doesn’t exist initially, it’s obfuscated into the JS code. The Problemĭevelopers that don’t want other people to be able to easily download their videos usually protect their content by obfuscating the code or loading it over JS. Nevertheless, the process of programmatically (headless) downloading files loaded with VideoJS, as is the case for OpenLoad, is pretty interesting, so I thought I should share my approach. The files belonged to them, and OpenLoad has an API designed for this, but I didn’t find out about it until it was too late. puppeteerrc.cjs (or came up to me recently with the task of downloading a few video files hosted via OpenLoad. Puppeteer uses several defaults that can be customized through configurationįor example, to change the default cache directory Puppeteer uses to installīrowsers, you can add a. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Your project folder (see an example below) because not all hosting providers Heroku, you might need to reconfigure the location of the cache to be within If you deploy a project using Puppeteer to a hosting provider, such as Render or The browser is downloaded to the $HOME/.cache/puppeteer folderīy default (starting with Puppeteer v19.0.0). When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to
0 kommentar(er)
