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

207 Multi-Status response not parsed correctly #83

Open
tipa opened this issue Feb 26, 2023 · 0 comments
Open

207 Multi-Status response not parsed correctly #83

tipa opened this issue Feb 26, 2023 · 0 comments

Comments

@tipa
Copy link

tipa commented Feb 26, 2023

I am making a Propfind request like this:
var response = await client.Propfind("/some/file.name", new PropfindParameters());

This XML request is sent over the wire:

<?xml version="1.0" encoding="utf-8"?>
<D:propfind xmlns:D="DAV:">
  <D:allprop />
</D:propfind>

The server responds with 207 Multi-Status (which is unusual (most servers would return 404 - Not Found in this example) but probably within the WebDAV specs):

<?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:">
<D:response>
<D:href>/some/file.name</D:href>
<D:propstat>
<D:prop>
</D:prop>
<D:status>HTTP/1.1 404 Not Found</D:status>
</D:propstat>
</D:response>
</D:multistatus>

I need to find out what status(es) the server responds with (detect the 404), but it appears like the PropertyStatuses field is not populated correctly:

image

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

1 participant