eDeviser: I was able to observe the issue firsthand thanks to the test credentials provided by Lukas (thanks!).
What I’m seeing is that tapping/clicking on a text file (the only file I have handy in the test instance) displays the contents of that file on a page. That page has a "Download" button, which, when clicked, triggers the HTTP 400 error. The URL that it tries to download when this fails is of the form http://[domain]/seafhttp/files/[uniqueID]/filename.txt.
Now when I get back to the file listing, if I long-press on the text file and choose "save link" from the context menu, the download goes through and the URL downloaded is of the form http://[domain]/lib/[uniqueID]/file/filename.txt. However the contents of the file that was actually downloaded is a HTML login page, not the text file.
eDeviser: I was able to observe the issue firsthand thanks to the test credentials provided by Lukas (thanks!).
What I’m seeing is that tapping/clicking on a text file (the only file I have handy in the test instance) displays the contents of that file on a page. That page has a "Download" button, which, when clicked, triggers the HTTP 400 error. The URL that it tries to download when this fails is of the form http://[domain] /seafhttp/ files/[ uniqueID] /filename. txt.
Now when I get back to the file listing, if I long-press on the text file and choose "save link" from the context menu, the download goes through and the URL downloaded is of the form http://[domain] /lib/[uniqueID] /file/filename. txt. However the contents of the file that was actually downloaded is a HTML login page, not the text file.
Can you please confirm you’re seeing the same?