Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dropbox calls fail with 404
See original GitHub issueI get a strange behavior where Uppy’s requests to dropbox return 404 when selecting a file or folder.
After examining the OPTIONS requests I could see that folder names or file names have %2F just before their name, like so:
<companion domain>/dropbox/list/%2F<folder name>
or
<companion domain>/dropbox/get/%2F<file name>
Is this the cause for the 404?
I run Companion behind Apache as a reverse proxy with React in the frontend.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Call get_preview http method returning 404 error
I had created the file 'word.docs' under the root folder. Request the api v2 method get_preview with the path for this file return...
Read more >Troubleshoot shared links - Dropbox Help Center
Whether you sent or received a shared link, it may fail to work or show a 404 error. If this happens, check the...
Read more >Dropbox shared link is not working or returns error (+Video)
If the shared link is not working · 1. The file or folder containing it had been deleted · 2. The link is...
Read more >DropBox Activities - Download File Fails - Bad Request ...
I am using the new DropBox activities (“UiPath. ... was user error, I would assume I would be getting a different error, such...
Read more >Error in value[[3L]](cond) : Cannot open data source - shiny
Error : HTTP 404 GET https://api.shinyapps.io/v1/applications/416524 Not Found ... For me I have my app.r & www files in my dropbox & I...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The same problem over Nginx… someone has a solution?
Ok, finally resolved 😃
It was not a CORS issue, rather an Apache configuration: I run Companion behind Apache as a reverse proxy.
For URLs that contain encoded path separators, Apache 2.4, by default, will refuse them with a 404 (Not found) error.
The solution is to add the following to its configuration: