bug in get_temporary_link / special characters

[Martin T.3]

Hi guys,

I'm playing around with the dropbox v2 api and found a problem which I'm fear might be a bug:

Whenever I call "get_temporary_link" related to a file with a special character ( like German Umlaut ä ) in it's name, the api returns a temporary link that results in an error 500.

All other files without those special characters work fine.

German Umlaut in the path (as long as they are not part of the filename) are also causing no problems.

Any idea?

Further tests: tried various de/encodings of the path, all resulted in no temporary_link returned. So I guess the path I provide is correct, Dropbox finds something in the database, but something is wrong with the temporary_link / response.

best regards, Martin

[Mark]

There is currently a service issue affecting shared links which is resulting in 500 errors which could explain your issue... however, as I dont have a clue about the API I cannot comment on if its actually a bug with that or not. 

[Greg-DB]

Thanks for the report Martin! We're looking into it.

[q. bodong]

The same problem to seek help.

[q. bodong]

Chinese file name will also appear this error

[Greg-DB]

This is fixed now. Please let us know if you're still seeing any issues.

[Martin T.3]

Thanks, Gregory, it works for me now!
I didn't try Chinese characters, but with German umlaut it's fine 🙂

Cheers, Martin

[Martin T.3]

Sorry, but found another issue now:

The filename provided in the download popup (I assume it's part of the Content-disposition - http-header) is cropped. In case there's a blank inside the original filename, it crops the filename at the blank's position.

E.g. original filename

my_filename_got_no_blanks.pdf -> works fine, provides full name
my_filename_got blanks.pdf -> provides just "my_filename_got"

😞

Thanks for looking into, Martin

[Greg-DB]

Hi Martin, can you share a screenshot of that so I can make sure I understand the issue and get it to the right people? Thanks in advance! 

[Martin T.3]

Sure, no problem:

First screenshot: everything fine, I'm using the /download endpoint and set the HTTP-Header

Content-Disposition: attachment; filename="Protokollauszug_Entwurf_TOP 6_PV 6.Juni 2016.pdf";

myself. Downloaded File is named correct.

Second screenshot: the bug: now I'm using the endpoint /get_temporary_link
and redirect to the returned URL. The filename is cropped at the first position of a blank

Third screenshot: again the /get_temporary_link endpoint, but this time with a
file that doesn't contain a blank in it's name: everything is fine.

Hope that helps!

best, Martin