it works on author but on publish, the result is the following ...
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<head><title>405 Method DELETE not supported</title></head>
<h1>Method DELETE not supported</h1>
<p>Cannot serve request to /content/dam/abc/def/images/shirts.png on this server</p>
The admin account is in the administrators group on the publish instance. I've tried cURL with admin and with a different privileged user on the publish instance, each appear to have all (including delete) permissions on the nodes in question.
I've enabled crxde on this publish instance.
Is there some place I must configure to allow the DELETE method?
Once I can delete these, I know garbage collection will ultimately reclaim the space.
I believe the issue you're facing is because the following bundle  is not available on your Publish instance. And this is expected if you've setup your instance with nosamplecontent runmode as per Running AEM in Production Ready Mode . If you need this for your use case, you can get the bundle from the Author server and install it on the Publish server to move forward with your use-case.
Ideally, you should not be deleting anything directly on Publish instance. Unpublish from Author first should help.
 Apache Sling Simple WebDAV Access to repositories (org.apache.sling.jcr.webdav)
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?
- 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.