AEM as a Cloud Service: 405 error for PUT and DELETE in Stage/Prod
In ÃÛ¶¹ÊÓÆµ Experience Manager as a Cloud Service (AEMaaCS), PUT and DELETE HTTP methods are blocked in Stage and Production environments. This behavior is intentional and helps protect content and system integrity. This article explains why the restriction exists and how to work around it using supported alternatives.
Description description
Environment
ÃÛ¶¹ÊÓÆµ Experience Manager as a Cloud Service (AEMaaCS), specifically in Stage and Production environments.
Issue/Symptoms
- PUT or DELETE requests return a 405 Method Not Allowed error
- Requests are blocked even though they work in Development environments
- CRXDE is not accessible in Stage or Production
Resolution resolution
This restriction is by design. In AEMaaCS, the WebDAV servlet that handles PUT and DELETE requests is only available in Development environments through CRXDE. Since CRXDE is not deployed in Stage or Production, these HTTP methods are blocked to prevent accidental or malicious changes.
To modify content in Stage or Production, use supported alternatives like the Sling POST servlet or AEM-provided APIs. These tools allow safe and controlled content manipulation without exposing the system to unnecessary risk.
For example, instead of using a PUT request to update a node, use a POST request with the appropriate parameters through the Sling POST servlet.