Skip to content

Following redirections in Client.propfind() not consistent #196

@airnandez

Description

@airnandez

I am evaluating webdav4 as an implementation of fsspec for accessing data stored in webDAV servers, in particular dCache and XRootD.

Depending on how some of those servers are configured, they may redirect requests to worker servers, in particular PROPFIND requests. I noticed that when that redirection occurs some functionality of webdav4 does not work because of the inconsistent policy for following redirections.

Client.propfind() has an optional argument to follow redirections, with default value False. Client.ls() uses profind and explicitly follows redirections but the methods below do not:

Is there any particular reason why those methods do not follow redirections? The issue is that for the same existing path to a remote file, Client.info() will raise an exception while Client.ls() will succeed, which I suspect is not intended.

I wonder if either Client.propfind()'s follow_redirects default value could be set to True or if follow_redirects=True could be consistently specified for all calls of Client.propfind().

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions