Hi Jörg,
I'm curious if your overload use case would be primarily for requests sent
by anonymous users?
I have been handling anonymous "sling/nonexisting" resources by using a
custom filter to force a redirect to the login page instead of sending back
a 404. In other words, the anonymous user
Hi,
The handling of 404s in Sling can be quite resource-intense, especially if
a custom error handler is provided, which renders a full-blown page.
This can lead to the situation, that the 404 handling is as complex and
resource-intense as handling a normal resource. This comes with these 2
sonarcloud[bot] commented on PR #19:
URL:
https://github.com/apache/sling-org-apache-sling-pipes/pull/19#issuecomment-1711595902
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
dependabot[bot] opened a new pull request, #19:
URL: https://github.com/apache/sling-org-apache-sling-pipes/pull/19
Bumps
[com.github.tomakehurst:wiremock-jre8-standalone](https://github.com/wiremock/wiremock)
from 2.27.2 to 2.35.1.
Release notes
Sourced from
aster/jdk_11_latest@tmp/withMaven90380d24/maven-spy-20230908-111809-904254541152507971207.log
[Pipeline] }
[withMaven] artifactsPublisher - Archive artifact pom.xml under
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT.pom
[withMaven] artifactsPublisher - A
Julian Reschke created SLING-12020:
--
Summary: resource resolver: alias metric has confusing name
Key: SLING-12020
URL: https://issues.apache.org/jira/browse/SLING-12020
Project: Sling
Issue
