[
https://issues.apache.org/jira/browse/SLING-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed SLING-8388.
-
> XSS possible in system console - servletresol
ole - servletresolver
>
>
> Key: SLING-8388
> URL: https://issues.apache.org/jira/browse/SLING-8388
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
>
ble in system console - servletresolver
>
>
> Key: SLING-8388
> URL: https://issues.apache.org/jira/browse/SLING-8388
> Project: Sling
> Issue Type: Bug
> Components: Resou
[
https://issues.apache.org/jira/browse/SLING-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-8388.
---
Resolution: Fixed
> XSS possible in system console - servletresol
[
https://issues.apache.org/jira/browse/SLING-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls reassigned SLING-8388:
-
Assignee: Karl Pauls
> XSS possible in system console - servletresol
-apache-sling-servlets-resolver/pull/4]
CC - [~kpauls], [~radu.cotescu]
> XSS possible in system console - servletresolver
>
>
> Key: SLING-8388
> URL: https://issues.apache.org/jira/br
Ashok Kumar created SLING-8388:
--
Summary: XSS possible in system console - servletresolver
Key: SLING-8388
URL: https://issues.apache.org/jira/browse/SLING-8388
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-5605.
---
> Wrong null annotations on ServletResolver interf
.
A good service should rather return null and not throw a runtime exception for
such cases. As the implementation is already doing this and existing clients
handle the null as a return value, we can safely adjust the javadocs
> Wrong null annotations on ServletResolver interf
[
https://issues.apache.org/jira/browse/SLING-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-5605:
Fix Version/s: API 2.12.0
> Wrong null annotations on ServletResolver interf
ons on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
> Issue Type: Bug
> Components: API
>A
[
https://issues.apache.org/jira/browse/SLING-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-5605:
Fix Version/s: (was: API 2.12.0)
> Wrong null annotations on ServletResolver interf
}}.
> Wrong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
> Issue Type: Bug
>
[
https://issues.apache.org/jira/browse/SLING-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5605.
Resolution: Invalid
> Wrong null annotations on ServletResolver interf
/r1735055].
> Wrong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
>
as well as the null annotations should be adjusted.
> Wrong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
>
> Wrong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
> Issue Type: Bug
>
never returned
> Wrong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
>
with the documentation in the context of
https://issues.apache.org/jira/browse/SLING-2920 was regretted by everyone,
because of the impact on all clients.
> Wrong null annotations on ServletResolver interface
> ---
>
> Key
ons on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
> Issue Type: Bug
> Components: API
>A
may break, if they
rely on the wrong behaviour (which was there right from the beginning). If
would therefore suggest to just adjust the javadoc and leave the implementation
as is. That is IMHO much less dangerous.
> Wrong null annotations on ServletResolver interf
ons on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
> Issue Type: Bug
> Components: API
&g
://svn.apache.org/r1735049]
> Wrong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
>
there always be a default servlet?
> Wrong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
>
ong null annotations on ServletResolver interface
> ---
>
> Key: SLING-5605
> URL: https://issues.apache.org/jira/browse/SLING-5605
> Project: Sling
> Issue Type: Bug
>
[
https://issues.apache.org/jira/browse/SLING-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-5605:
--
Assignee: Konrad Windszus
> Wrong null annotations on ServletResolver interf
Konrad Windszus created SLING-5605:
--
Summary: Wrong null annotations on ServletResolver interface
Key: SLING-5605
URL: https://issues.apache.org/jira/browse/SLING-5605
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-4939.
---
> ServletResolver implementation is too verb
Carsten Ziegeler created SLING-4939:
---
Summary: ServletResolver implementation is too verbose
Key: SLING-4939
URL: https://issues.apache.org/jira/browse/SLING-4939
Project: Sling
Issue Type
[
https://issues.apache.org/jira/browse/SLING-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-4939:
---
Assignee: Carsten Ziegeler
ServletResolver implementation is too verbose
[
https://issues.apache.org/jira/browse/SLING-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4939.
-
Resolution: Fixed
Changed in rev 1695057
ServletResolver implementation is too verbose
\] provide access to the Script Resource
Resolver in RenderContext|http://sling.markmail.org/thread/d5ujhidmsvb5l5ik]
[Sightly] Extend RenderContext to provide access to the ServletResolver
resource resolver
be wrapping it to prevent closing. See SLING-4352 for details.
[Sightly] Extend RenderContext to provide access to the ServletResolver
resource resolver
-
Key: SLING-4349
to the ServletResolver
resource resolver
-
Key: SLING-4349
URL: https://issues.apache.org/jira/browse/SLING-4349
Project: Sling
Issue Type
Radu Cotescu created SLING-4349:
---
Summary: [Sightly] Extend RenderContext to provide access to the
ServletResolver resource resolver
Key: SLING-4349
URL: https://issues.apache.org/jira/browse/SLING-4349
-3006. Someone with the right permissions should
resolve this issue.
Navigating to /system/console/servletresolver causes error 500
--
Key: SLING-3025
URL: https://issues.apache.org/jira/browse/SLING
)
Servlets
Navigating to /system/console/servletresolver causes error 500
--
Key: SLING-3025
URL: https://issues.apache.org/jira/browse/SLING-3025
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3025.
-
Resolution: Fixed
Navigating to /system/console/servletresolver causes error 500
[
https://issues.apache.org/jira/browse/SLING-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-3025.
---
Navigating to /system/console/servletresolver causes error 500
Dan Platon created SLING-3025:
-
Summary: Navigating to /system/console/servletresolver causes
error 500
Key: SLING-3025
URL: https://issues.apache.org/jira/browse/SLING-3025
Project: Sling
I attached a very simple patch, please somebody review it.
2013/8/20 Dan Platon (JIRA) j...@apache.org:
Dan Platon created SLING-3025:
-
Summary: Navigating to /system/console/servletresolver causes
error 500
Key: SLING-3025
plugin didn't
handle the case in which the {{url}} request parameter was not specified.
Navigating to /system/console/servletresolver causes error 500
--
Key: SLING-3025
URL: https
.
Thank you.
Navigating to /system/console/servletresolver causes error 500
--
Key: SLING-3025
URL: https://issues.apache.org/jira/browse/SLING-3025
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1880.
---
ServletResolver should log when a servlet is ignored due to not being in one
[
https://issues.apache.org/jira/browse/SLING-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-1880:
---
Assignee: Carsten Ziegeler (was: Felix Meschberger)
ServletResolver should log
- all other messages wrt servlet
resolving are logged with this log level as well.
ServletResolver should log when a servlet is ignored due to not being in one
of the allowed execution paths
ServletResolver should log when a servlet is ignored due to not being in one of
the allowed execution paths
---
Key: SLING-1880
URL: https://issues.apache.org
[
https://issues.apache.org/jira/browse/SLING-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-1121.
This can probably be closed.
ServletResolver not properly resolving custom error handler 500
, since this works as designed, even though it may seem
unexpected.
ServletResolver not properly resolving custom error handler 500 servlet/script
--
Key: SLING-1121
URL: https
/INTERNAL SERVER
ERROR status but not call the sendError method. Hence the 500.jsp will not be
called in this case.
Your using a Throwable script is quite correct and intended.
ServletResolver not properly resolving custom error handler 500 servlet/script
I'm trying to find all options for directing requests to different servlets.
I was glad if somebody could confirm that the following use cases are not
covered:
1. A wildcard for the name of the first node in the path, e.g. @scr.property
name=sling.servlet.paths value=\/.*?\/a\/b
2.
Thanks for the quick confirmation,
Marc
On Mon, Sep 14, 2009 at 10:51 AM, Vidar Ramdal vi...@idium.no wrote:
On Mon, Sep 14, 2009 at 10:46 AM, Marc Speck marcsp...@gmail.com wrote:
I'm trying to find all options for directing requests to different
servlets.
I was glad if somebody could
On Mon, Sep 14, 2009 at 10:51 AM, Vidar Ramdal vi...@idium.no wrote:
...you might be able to write your own ResourceProvider to
handle those cases
And there's OptingServlet [1], with an accept() method that lets you
fine-tune requests that a servlet accepts based on its registration
Hi,
On Mon, Sep 14, 2009 at 12:22 PM, Marc Speck marcsp...@gmail.com wrote:
On Mon, Sep 14, 2009 at 11:43 AM, Bertrand Delacretaz
bdelacre...@gmail.com wrote:
...using version.12 instead of version=12 should help here, 12
then becomes just another selector.
Excellent idea, parsing
On Mon, Sep 14, 2009 at 1:59 PM, Vidar Ramdal vi...@idium.no wrote:
On Mon, Sep 14, 2009 at 1:41 PM, Bertrand Delacretaz
bdelacre...@codeconsult.ch wrote:
Hi,
On Mon, Sep 14, 2009 at 12:22 PM, Marc Speck marcsp...@gmail.com
wrote:
On Mon, Sep 14, 2009 at 11:43 AM, Bertrand Delacretaz
55 matches
Mail list logo
