stephaneriel72 Like the custom.css file which still doesn't work on a Windows server...
I just discovered that this is a bug, which specifically affects Windows servers. For the LOGIN page, the Config::$document_root variable was not yet created, and therefore the calculated root path for custom.css was returning false. On non-Windows, it seemed to work, because it just returned the relative path. Anyway, this will be fixed in next release.
However, the above only affected the login page, and certainly does not affect mp4 videos. In fact, Files Gallery just loads the video source into <video src="PATH.MP$"> and that's it ... If your video does not play before loading completely, it means either ONE of the following must be true:
Your server doesn't send content-length or content-range headers, necessarily to load 206 partial content.
Or you are proxying the video via PHP. This would happen if your video is not in the servers document root.
Server streams partial content, necessary to display the video
You can check if PHP is proxying the file by opening browser developer tools > network, reloading page and clicking the video. What does the loading url for video look like? When loading files directly, which would be necessary, it would look like this. As you can see, combined with correct headers, it outputs multiple partial responses.
