That already comes close, but I was more thinking about a dedicated operation which indicates, that a required specialized servlet is missing. That could by default return a status 500 with a reasonable error message (so only one parameter necessary). I created https://issues.apache.org/jira/browse/SLING-9531 <https://issues.apache.org/jira/browse/SLING-9531> to track that. Thanks for your input, Konrad
> On 18. Jun 2020, at 15:30, Karl Pauls <karlpa...@gmail.com> wrote: > > https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#slingpostservlet-operations-1 > > obviously, that only helps if you have the client under your control. > > regards, > > Karl > > On Thursday, June 18, 2020, Karl Pauls <karlpa...@gmail.com> wrote: > >> I guess you could add a nop operation. >> >> regards, >> >> Karl >> >> On Thursday, June 18, 2020, Bertrand Delacretaz <bdelacre...@apache.org> >> wrote: >> >>> On Thu, Jun 18, 2020 at 2:46 PM Konrad Windszus >>> <konrad.winds...@netcentric.biz> wrote: >>>> ...Is there a simple way (like a certain parameter or request path >>> format) which prevents the >>>> Sling POST servlet from responding?... >>> >>> Not that I know, but my memory is bad for such things. >>> >>>> If not, do you think that this would be a useful addition? >>> >>> I think so - maybe something like the PathBasedAcceptor [1] created >>> for SLING-8110 could help set stricter requirements for that default >>> servlet to execute. >>> >>> -Bertrand >>> >>> [1] https://github.com/apache/sling-org-apache-sling-servlets- >>> resolver/blob/master/src/main/java/org/apache/sling/ >>> servlets/resolver/internal/PathBasedServletAcceptor.java >>> >> >> >> -- >> Karl Pauls >> karlpa...@gmail.com >> >> > > -- > Karl Pauls > karlpa...@gmail.com
