Open tedgin opened 4 years ago
Interesting, confirmed bug. Is this currently affecting/breaking a webdav client of yours? It seems the commonly used clients over the past years haven't been bothered by this. When/if clients end up sending follow-up requests with double slashes, they are currently normalized both by Apache and by iRODS path parsing to end up at the correct object.
It's not causing any issues that I know of. I noticed it while debugging an unrelated issue we were having.
Hi, I just run into an issue when using rclone (https://rclone.org). It throws an error:
2022/03/11 08:38:42 ERROR : /Dockerfile: Entry doesn't belong in directory "" (contains subdir) - ignoring
due to this extra /
in the returned path.
I just encountered this same error with rclone.
When a
PROPFIND
request is made on a collection with the URLhttps://host.domain/collection/
, the paths to the members of/collection/
in theDAV:multistatus
response document all have an extra forward slash in the URL immediately after the/collection/
prefix. For example, ifobject
is a member ofcollection
, its URL path in the response will be/collection//object
. Here's a real example.