Skip to content

[Upstream #2163][WebDAV] Follow permanent endpoint redirects during backup and restore #99

Description

@SingLinkNetwork

Source

Scope

This tracks only the WebDAV permanent-redirect portion. The Android local file-picker portion is tracked separately in #97.

Root cause

The bundled WebDAV client retries 302 redirects itself but does not recognize HTTP 301. A canonical WebDAV endpoint that returns 301 is therefore treated as failed.

Fix and verification

  • Normalize HTTP 301 to the client's existing safe 302 retry path, preserving the WebDAV method and request body.
  • Regression test uses a local WebDAV-like endpoint that returns 301 for OPTIONS / and succeeds at the redirected path.
  • Local full Flutter tests and static analysis pass.
  • This issue remains open until the stacked draft PR passes full GitHub Actions and is merged/released.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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