Trying to move Ivy to an HTTP-based publish model, we discovered that it doesn't perform a MKCOL before doing a PUT.

The problem is that when Ivy attempts to publish to a URL resolver via HTTP, it does not adhere to the WebDav requirement that you create the parent path (parent collections) with a MKCOL command before the PUT command. Ivy incorrectly just attempts to PUT artifacts to a path which hasn't been created.