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.
Source
Moved Permanently.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
OPTIONS /and succeeds at the redirected path.