Į:80 11.22.33.44 - "HEAD /basic-auth-protected-path/some-song.mp3 HTTP/1.1" 401 246 "-" "ddg_android/5.108.0 ( Android API 30)"īrowser is DDG 5.108.0 on latest Lineage 18.The DuckDuckGo app provides the most comprehensive online privacy protection with the push of a button.
Request for playing a file in browser: worksĮ:80 11.22.33.44 - username "GET /basic-auth-protected-path/some-song.mp3 HTTP/1.1" 200 1929600 " " "Mozilla/5.0 (Linux Android 11) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/.104 DuckDuckGo/5 Safari/537.36"Į:80 11.22.33.44 - username "GET /basic-auth-protected-path/some-song.mp3 HTTP/1.1" 206 3229852 " " "Mozilla/5.0 (Linux Android 11) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/.104 DuckDuckGo/5 Safari/537.36"Īfter hitting the "Download" menu option in the player via the "." Menu: Failing HEAD request because basic auth is not honored, so download fails.Īlso, there is a different useragent suddenly. This is the corresponding server log of such a session: mp3 file in a http auth protected directory is being requested and played in the browser, then in the player widget the. This is because using the download context menu causes an additional HEAD request which is agnostic of the existing authentication in the session. When doing this with files that are under http basic protection, the display/playing of a file in the browser works, but then the download fails. Since there is no "download this file/download this link" in the context menu when pressing a link to a file, files must be opened in the browser window before downloading.
May I add an observation, that should also be considered when working on download problems: We are currently running a project to hopefully fix once and for all our download issues, we'll re-add this to the list :)
0 kommentar(er)
