[
https://issues.apache.org/jira/browse/SLING-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-9531:
-----------------------------------
Description:
Very often POST servlets rely on OSGi DS which is dynamic. If for whatever
reason the specialized servlet component is not running, Sling falls back to
the Default POST Servlet. That is very often not intended. To prevent the
Default POST Servlet from doing any repository modification operations a new
operation should be added which leads to a 500 error and the status message,
that a more specific servlet is necessary.
Compare with the discussion from
https://lists.apache.org/thread.html/r00d54024759efe1f0456008e21a994f5bafe512bf65ff9bc1c767999%40%3Cdev.sling.apache.org%3E
Currently there is only the very generic NOP operation which does not hint at
the fact that a necessary servlet is not deployed.
was:
Very often POST servlets rely on OSGi DS which is dynamic. If for whatever
reason the specialized servlet component is not running, Sling falls back to
the Default POST Servlet. That is very often not intended. To prevent the
Default POST Servlet from doing any repository modification operations a new
operation should be added which leads to a 500 error and the status message,
that a more specific servlet is necessary.
Compare with the discussion from
https://lists.apache.org/thread.html/r00d54024759efe1f0456008e21a994f5bafe512bf65ff9bc1c767999%40%3Cdev.sling.apache.org%3E
> Add operation which indicates that a more specific servlet is needed
> --------------------------------------------------------------------
>
> Key: SLING-9531
> URL: https://issues.apache.org/jira/browse/SLING-9531
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Servlets Post 2.3.36
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Servlets POST 2.3.38
>
>
> Very often POST servlets rely on OSGi DS which is dynamic. If for whatever
> reason the specialized servlet component is not running, Sling falls back to
> the Default POST Servlet. That is very often not intended. To prevent the
> Default POST Servlet from doing any repository modification operations a new
> operation should be added which leads to a 500 error and the status message,
> that a more specific servlet is necessary.
> Compare with the discussion from
> https://lists.apache.org/thread.html/r00d54024759efe1f0456008e21a994f5bafe512bf65ff9bc1c767999%40%3Cdev.sling.apache.org%3E
> Currently there is only the very generic NOP operation which does not hint at
> the fact that a necessary servlet is not deployed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
