joerghoh opened a new pull request, #102:
URL: https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/102
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
Joerg Hoh created SLING-12021:
-
Summary: Update to Parent 52
Key: SLING-12021
URL: https://issues.apache.org/jira/browse/SLING-12021
Project: Sling
Issue Type: Task
Components:
[
https://issues.apache.org/jira/browse/SLING-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763355#comment-17763355
]
Joerg Hoh commented on SLING-10357:
---
[~petitbear68] since some time there is
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/1007/
for details.
No further emails will be sent until the status of the build is changed.
Why do we need special casing outside of the error handler. Couldn't the
error handler do the same?
Regards
Carsten
On 08.09.2023 18:13, Jörg Hoh wrote:
Hi,
The handling of 404s in Sling can be quite resource-intense, especially if
a custom error handler is provided, which renders a
