Hi, Have your servlet implement the OptingServlet [1] interface and return false from the accepts method if you encounter the ":operation" request parameter.
This way, your servlet will not be called in these circumstances and thus the search for a servlet to call will continue ultimatelively leading to the default POST servlet. Regards Felix [1] http://sling.apache.org/apidocs/sling5/index.html?org/apache/sling/api/servlets/OptingServlet.html On 26.10.2010 19:07, Carl Hall wrote: > I have a node, /var/proxy/scribd, that has sling:resourceType='sakai/proxy' > which triggers a proxy handling servlet. While in development, I often need > to change properties on this node or delete the node entirely. Since my > servlet handles POST, it catches my call when I do "curl -F > :operation=delete http://localhost:8080/var/proxy/scribd"; leaving me with > the results of the servlet processing which is a 400 return code and thusly > doesn't run the delete post processor. Is there a way I can not run the > resource type processor or do I need to add a catch for the delete command > so my servlet stops processing gracefully to allow deletion? >
