You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e76edcb
Browse filesBrowse the repository at this point in the historyBrowse files
DAVError gained a status attribute in 3.6.0, but a failing status
inside a multistatus (a 507 <propstat> or <response> status in a
PROPFIND reply, say) raised a ResponseError with status None, so the
code could only be read from the message text. That check now
passes the code, or None for a status line it cannot parse. For
consistency the parse_* methods' non-2xx raises go through
error_from_response(), keeping body and preconditions too, and the
foreign-href sync 507 passes its code.
Prompt: A 507 from propfind comes back as a ResponseError with status set to None
Assisted-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
A `ResponseError` raised for a failed PROPFIND, REPORT or sync-collection reply, or for a failing `<propstat>` status inside a multistatus (e.g. `507 Insufficient Storage`), now has its `status` attribute set; it was `None`, so the code had to be parsed out of the message. The failed replies also keep `body` and `preconditions`, like other `DAVError`s.
0 commit comments