You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mirror of #213 on the web frontend. If I upload foo#1.txt with curl, the download button gives a 404 because the get link has an unencoded #, so the server will not find /get/hash/foo.
If I upload the same file with the frontend, the download button works, but the filename is truncated at the #.
The text was updated successfully, but these errors were encountered:
thanks for reporting the issue, I was able to reproduce
as you mentionedm for the curl upload with frontend giving 404 the problem is that the file is uploaded as foo%231.txt while the link points to foo#1.txt. I will look into urlencoding the filename in the frontend link. minor thing is that will produce urlencoded url probably for every non-ascii chars, including non latin alphabets
I will look into the js for the part on the frontend truncating at #
Mirror of #213 on the web frontend. If I upload
foo#1.txt
with curl, the download button gives a 404 because theget
link has an unencoded#
, so the server will not find/get/hash/foo
.If I upload the same file with the frontend, the download button works, but the filename is truncated at the
#
.The text was updated successfully, but these errors were encountered: