Thanks Aneet,
I was running with nosamplecontent, not because it was prod, but because I didn't want sample content. Indeed, the publish was missing "Apache Sling Simple WebDAV" bundle -- I copied it over from the author and installed it on publish, but still received the 405.
It wasn't until I reconfigured this bundle's config (to match the author's) that I was able to successfully delete the files via cURL.
Any idea why?
I changed:
- Root Path from -- /dav to /crx/repository
- Non Collection Node Types -- added dam:Asset
mirroring the author's values for Apache Sling Simple WebDAV.
Can you tell me what these fields represent and why it was required for my cURL -X DELETE commands to work?
I appreciate the advice about deactivating instead, but the goal here was simply to remove the largest binary files of various types. I did a query of the largest .zip, .exe, .jpg, .psd, .iso, etc. files, and used this to form my list of files to delete. The instances are for Dev, so consistency was not required, the more important objective was getting these instances running on the available limited disk of our Dev hardware. Additionally, I wanted to delete the largest files on both instances, not necessarily files that were active or inactive.
Thanks again!
