-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tar archive encodes file-names wrongly #2255
Comments
CC @gmgigi96 |
Thanks @individual-it. I tried in my test environment (and also in our production) but I wasn't able to reproduce it (I tried with WinRAR 6.02). Could you give more details on your current reva setup (like the storage provider you used, ...)? Thanks |
@gmgigi96 I'm using ocis from the master branch https://github.com/owncloud/ocis/ it has a folder called when I unpack it with PHP
the file name is only can you try to open that file with WinRAR |
AFAIK ocis uses the ocis storage per default |
@individual-it I can see with no problems the content of the tar you pointed me out, as you can see from the figure I also tried with different different storage providers also ( |
@gmgigi96 yes that might be, I will have to dig deeper |
After reading more about tar, I think this is a general issue of tar, it does not support officially anything else than ASCII I will close this issue and proposing to switch to ZIP also on Linux systems |
originally in owncloud/ocis#2743
Describe the bug
file-names with non-latin characters are not displayed correctly with some tar tools
Steps to reproduce
Steps to reproduce the behavior:
using ocis & owncloud web:
Windows NT
is not send in theUser-Agent
header. So on Windows the user-agent need to be faked or usecurl
.tar
file as download, if you are given a.zip
file the user-agent header contains the stringWindows NT
Expected behavior
file-names should contain all non-latin characters
Actual behavior
This works fine with Linux
tar
command, but not with any Windows tool I tried or PHPInstead I get all non-latin characters removed from the file-names and an additional folder called
PaxHeaders.0
, this folder contains text files, where the content is the correct name of the actual filePaxHeaders.0
:27 path=my_data/öäü.txt
Additional context
This is ether a problem in how the tar files are constructed in ocis or some widely used library for clients has an issue
The text was updated successfully, but these errors were encountered: