[Bug]: webdav files download Base64 encoded about server

[the-djmaze]

The response in the browser tools looks the same for any sort of binary download AFAIK - e.g. Download https://github.com/the-djmaze/snappymail/releases/download/v2.36.0/snappymail-2.36.0.zip. So I'm not sure that's a good indicator anything is being encoded in base64.

You are right. I've tested this further and Firefox indeed shows almost all in base64 instead of binary data.
Some tests i did, didn't show in base64, but now they do.

So this is a browser thing.

[szaimen]

Hi, which nc version?

[the-djmaze]

I've tested v25 and up to v27.1.8.

@einhander should report here which version he/she/it/them uses.

[einhander]

@the-djmaze, I use nextcloud 27.1.7
EDIT: The same with nextcloud 27.1.8

[joshtrichards]

I don't follow. The original PDF is downloaded. Are you suggesting that the downloaded file (https://nextcloud.example.com/remote.php/webdav/Documents/Nextcloud%20flyer.pdf) is base64 encoded when saved at the client? Because that's not my experience testing and checking the downloaded file from any of my Nextcloud Server instances. It would be a serious bug if so.

The response in the browser tools looks the same for any sort of binary download AFAIK - e.g. Download https://github.com/the-djmaze/snappymail/releases/download/v2.36.0/snappymail-2.36.0.zip. So I'm not sure that's a good indicator anything is being encoded in base64.

And Content-Transfer-Encoding isn't a valid header used in HTTP to my knowledge (well one can specify it but it doesn't do anything).

The linked bug report says this:

Click on save to local PC or Nextcloud

So it sounds like this is happening even when Nextcloud isn't in the picture.

If I'm missing something, feel free to clarify.