Skip to content
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

Owncloud - virtual files smaller <1KB - problems with syncing #8248

Closed
hdijkema opened this issue Nov 23, 2020 · 2 comments
Closed

Owncloud - virtual files smaller <1KB - problems with syncing #8248

hdijkema opened this issue Nov 23, 2020 · 2 comments
Milestone

Comments

@hdijkema
Copy link

Expected behaviour

Syncing a file <1Kb (827bytes) should sync its 827 bytes to the windows drive when I try to open it and it resides on the owncloud server (virtual files mode).

Actual behaviour

The local file becomes 0bytes. This is with virtual file support. So, when I try to open the file, which resides on the server and is smaller than 1KB (827 bytes in this case), it first is downloaded, but when I open it it is empty; and when I look it's 0 bytes. When I open it in the web interface, it is oke. When I sync a new file from local to server both files are the same size (client and server), but when I clean up the space and reopen it with e.g. notepad++ or notepad, the syncing starts, and next, notepad(++) is openened with an empty file. If I choose 'make available always', it will sync nicely and when I open the file, it contains the 827 bytes it had.

Steps to reproduce

  1. Create a virtual files share.
  2. Put a file of <1KB (827 bytes?) in it, a text file.
  3. Make room, i.e. cleanup the files to the server
  4. Open a file from the cloud by opening it with notepad.
  5. Nothing will be shown.

Server configuration

Operating system: Debian 9
Web server: Apache 2.4, with Reverse proxy.
Database: PostgreSQL
PHP version: 7.2
ownCloud version: 10.5.0 stable
Storage backend (external storage): not applicable, just normal ext4 file system.

Client configuration

Client version: 2.7.1
Operating system: Windows 10
OS language: Dutch

Qt version used by client package (Linux only, see also Settings dialog): not applicable

Client package (From ownCloud or distro) (Linux only): not applicable

Installation path of client: Windows, standard

Logs

? Client or server? Let's just show what happens.

These are the files...

image

Making room...

image

It has been done...

image

Now double click on the item...and the result...

image

It starts having trouble...when I try to make it available always, it keeps syncing....When I make room on it, it puts it in the cloud again, and when I make it available always again, it hasn't been damaged, the file is there.

image

  1. See attached files.
    This is recorded while doing the above actions.

OWNCLOUD probleem.zip

  1. Web server error log:
  • Nothing went wrong, no error logging.
  1. Server logfile: ownCloud log (data/owncloud.log):
  • Nothing went wrong, no error logging.
@TheOneRing TheOneRing added this to the 2.7.2 milestone Nov 23, 2020
TheOneRing added a commit that referenced this issue Dec 1, 2020
The issue was caused by gziped responses not providing a
content lenght header.

Fixes: #8248
TheOneRing added a commit that referenced this issue Dec 1, 2020
The issue was caused by gziped responses not providing a
content lenght header.

Fixes: #8248
@jnweiger
Copy link
Contributor

jnweiger commented Dec 1, 2020

Reproduced on win10 with owncloudclient 2.7.1

testpilotcloud-2.7.2.2620.x64.msi fixes the issue.

@TheOneRing
Copy link
Member

@hdijkema thx for reporting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants