0-length files and auth setup (apache)

[lajonss]

I was unable to send files through a mount point.
Server: httpd 2.4.62-1 (arch linux)

I had read-only access for unauthenticated users configured:

        # Allow universal read-access, but writes are restricted
        # to the admin user.
        <RequireAny>
            Require method GET POST OPTIONS
            Require user myuser
        </RequireAny>

<ip> - - [12/Sep/2024:11:48:31 +0200] "PUT <file> HTTP/2.0" 401 1311
<ip> - myuser [12/Sep/2024:11:48:31 +0200] "PUT <file> HTTP/2.0" 201 227
<ip> - - [12/Sep/2024:11:48:31 +0200] "HEAD <file> HTTP/2.0" 200 -
<ip> - - [12/Sep/2024:11:48:32 +0200] "PUT <file> HTTP/2.0" 401 1311

The problem was gone when I disabled the read-only access.

        Require user myuser

<ip> - - [12/Sep/2024:12:23:35 +0200] "PUT <file> HTTP/2.0" 401 1311
<ip> - myuser [12/Sep/2024:12:23:35 +0200] "PUT <file> HTTP/2.0" 201 227
<ip> - - [12/Sep/2024:12:23:35 +0200] "HEAD <file> HTTP/2.0" 401 1311
<ip> - myuser [12/Sep/2024:12:23:35 +0200] "HEAD <file> HTTP/2.0" 200 -
<ip> - myuser [12/Sep/2024:12:23:35 +0200] "PUT <file> HTTP/2.0" 204 -

I'm using digest auth and https.

[ArnyminerZ]

Hi, I don't know much about your setup, but according to I can see, everything is working fine. You are only authorizing GET, POST and OPTIONS, which according to your logs, are accepted correctly, but you have not authorized PUT, which is correctly rejected:

<ip> - - [12/Sep/2024:11:48:32 +0200] "PUT <file> HTTP/2.0" 401 1311

What is your question? Are you trying to use WebDAV? What are you trying to achieve?

[lajonss]

What is your question?

I didn't make my intentions clear, I'm sorry.

It's either a heads-up for someone who could be having similar issues or a bug report if it's not intended behaviour of DAVx⁵.

Are you trying to use WebDAV? What are you trying to achieve?

Yes, using a DAVx⁵ mount point and self-hosted WebDAV on apache. Material Files app did function correctly with the hybrid auth setup, DAVx⁵ did not, so I thought it could be a bug.

[ArnyminerZ]

It's either a heads-up for someone who could be having similar issues or a bug report if it's not intended behaviour of DAVx⁵.

So you are suggesting that they just disable read-only? I'm not sure what you mean.

Either case, I think that read-only should be working fine on DAVx⁵, no errors should be thrown.

Which, by the way, this is not how read-only works in DAV. The server must be configured to set a folder as read-only, not the HTTP proxy (Apache). DAV clients perform a propfind on the collection to check whether the authorized user has write permissions. You really shouldn't configure write access based on HTTP operations. Just to make it clear, this has to be configured in the DAV server.

[lajonss]

Thanks for the clarification.

I'm using apache as the WebDAV server. The read-only setup in my config came from the template on Arch Wiki.