[
https://issues.apache.org/jira/browse/SLING-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh resolved SLING-9441.
------------------------------
Resolution: Duplicate
Resolved as duplicate of SLING-9896
> Sling POST servlet responds with 500 if target is not modifiable
> ----------------------------------------------------------------
>
> Key: SLING-9441
> URL: https://issues.apache.org/jira/browse/SLING-9441
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Post 2.3.36
> Reporter: Lars Krapf
> Priority: Minor
>
> In case a POST is attempted to a node that the request session does not have
> write access to, the POST servlets throws a 500, e.g.
> {code}
> 04.05.2020 21:34:09.162 *ERROR* [xxx.xxx.xxx.xxx [1588628049158] POST
> /content/cmo/us/en/home/users/geometrixx/[email protected]/fSPiyhliJm
> HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation
> Exception during response processing.
> org.apache.sling.api.resource.PersistenceException: Unable to create node at
> /content/cmo/us/en/home/users
> at
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.create(JcrResourceProvider.java:477)
> [org.apache.sling.jcr.resource:3.0.20]
> {code}
> Since this is actually a client error I think a 4xx response would be better
> suited, and make it more obvious that such errors can be safely ignored when
> doing health monitoring.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
