Hi! I’ve been trying to upload files to seafile using the rest api and ran into issues until I discovered that one of my keys had a lower case letter while seafile was expecting an upper case one. I believe that keys should be case insensitive however.
The exact error I had was (but I think case insensitivity should be checked everywhere) was while sending a file and creating the multipart data.
After reciving the upload link, you may upload files by API such as Upload file
And, the content-disposition data is not required though. Maybe I do not know how you use the
API for file uploading, could you please give us the details of the whole http requests codes。
Furthermore, when I am using the thirdparty API tools for testing, the Capitalized content-disposition may be a standard input.
I understand how uploading a file works, my post is about the content of the POST request sent to upload a file.
I’m using a tool that creates the request for me, and it turns out it didn’t capitalized the D in Content-Disposition resulting in an obscure “bad request” error message.
I believe that capitalization is supposed to be optional and if that’s the case, then seafile should handle it as such
For more standard http protocol support, you can enable and use go fileserver instead. We don’t plan to change the C fileserver a lot with regards to http protocol details, to avoid unexpected bugs. seafile.conf - Seafile Admin Manual
If the C fileserver works without problems you can continue to use it. The go fileserver has been used by some large deployments and we think it’s production ready. There may still be some minor bugs though.
Some point in the future we’ll make go fileserver the default. For now we want a more gradual switching procedure, to collect more feedbacks from users.