transloadit / uppy-server

[DEPRECATED] 'Uppy Server' was renamed to 'Companion' and lives inside the Uppy repo no
https://github.com/transloadit/uppy/tree/master/packages/%40uppy/companion
MIT License
114 stars 27 forks source link

404 HTTP error for Dropbox file operations #80

Closed vgiotsas closed 6 years ago

vgiotsas commented 6 years ago

After authenticating with Dropbox, only the list operation of the root folder works. When I try to list Dropbox sub-folders or get files, the standalone uppy-server returns 404 error because it appends an extra / before the file or folder name, e.g.

/dropbox/get//filename.ext was not found on this server.

When I manually remove the additional / and paste the link directly to the browser I get the following message:

"No endpoint, file written to uppy server local storage"

In the uppy-server output I see the following error message:

uppy: 2018-04-04T01:51:00.891Z [error] provider.dropbox.size.error Error in call to API function "files/get_metadata": request body: path: 'filename.ext' did not match pattern '(/(.|[\r\n])*|id:.*)|(rev:[0-9a-f]{9,})|(ns:[0-9]+(/.*)?)'
ifedapoolarewaju commented 6 years ago

When I try to list Dropbox sub-folders or get files, the standalone uppy-server returns 404 error because it appends an extra / before the file or folder name

are there particular steps that I should follow to reproduce this? I am asking because it seems to work fine for me on the example page here https://uppy.io/examples/dashboard/ Are you also noticing the same error on the example page?

ifedapoolarewaju commented 6 years ago

closing this as I cannot reproduce