slachiewicz commented on issue #630: URL: https://github.com/apache/maven-wagon/issues/630#issuecomment-5225541830
Partial progress worth recording against the original list, so the remaining work is clear. **Moved since 2020:** - *Redirects on `MKCOL` are completely ignored.* `WagonRedirectStrategy` now includes `MKCOL` among the methods it follows redirects for. The comment there is honest about the limit: it covers "the most basic case where the redirection relocates to another collection which has an existing parent collection". So improved, not closed. - The provider no longer depends on `jackrabbit-webdav` at all (#898). The three requests it actually issues — `MKCOL`, `PROPFIND`, `HEAD` — plus multistatus parsing now live in the provider, which makes the RFC 4918 behaviour visible and changeable in one place rather than spread across a third-party library. That does not fix any of the items below, but it removes the main obstacle to fixing them. **Unchanged:** - `PUT` returning 409 when parent collections do not exist is still not handled; there is no reference to 409 anywhere in the HTTP or WebDAV provider sources. - `MKCOL` status handling in `WebDavWagon.mkdirs()` still recognises only `201 Created` and `405 Method Not Allowed`, treating everything else as a reason to keep walking backwards, then failing on anything that is not `201` on the way forward. - The tests still exercise WebDAV through the HTTP test base. On the proposal in the original description: the deprecation notice on this provider points at 4.0.0, which has never been released — the shipping line is 3.5.x and is expected to stay for the time being. So "it will be removed anyway" is not currently a reason to leave these unfixed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
