> Every download could be directed directly to the Downloadmanager. Oxide doesn’t know that a download is a download until it has issued the request and gotten a response. So it can’t delegate the download to UDM upfront. What has to happen for this use case to work, is that downloads need to be handled by oxide itself (but that has serious implications on the strict lifecycle policies).
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1548020 Title: Direct download fails on seafile/nextcloud server Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I'm hosting a webserver with seafile. When I click on the Download link direktly, then choosing the app for opening, the Download aborts because of Http400 Error. This could be because the Download token from the server are working just for one time. Nevertheless, if do rightclick on the download link and select "save as", the download works pretty fine. I think, when clicking on such a link, a request to the server is issued, which invalidates the link for subsequent requests. The headers from the response to that request are then passed to the download manager which will initiate the download by issuing the request again, and the first request initiated by the browser is cancelled. That’s indeed a bug in how downloads are handled in the browser. If nessesary I can provide a temporary download link for testing the issues. This happend on my Nexus 4 with OTA9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1548020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
