sling:match and mapping

matching to be matched back when mapping content paths to URLs" [1] https://issues.apache.org/jira/browse/SLING-2560 [2] http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html Cheers Ben -- Ben Peter M: +49 151 27580088

[jira] [Resolved] (SLING-3119) Startup Filter: move to HTTP filter to prevent authentication before startup has completed

[ https://issues.apache.org/jira/browse/SLING-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Peter resolved SLING-3119. -- Resolution: Fixed Thank you, Bertrand! > Startup Filter: move to HTTP filter

[jira] [Updated] (SLING-3119) Startup Filter: move to HTTP filter to prevent authentication before startup has completed

[ https://issues.apache.org/jira/browse/SLING-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Peter updated SLING-3119: - Attachment: SLING-3119.patch attaching patch > Startup Filter: move to HTTP filter

[jira] [Updated] (SLING-3119) Startup Filter: move to HTTP filter to prevent authentication before startup has completed

[ https://issues.apache.org/jira/browse/SLING-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Peter updated SLING-3119: - Description: The current StartupFilter implementation is a Sling filter which prevents requests from

[jira] [Created] (SLING-3119) Startup Filter: move to HTTP filter to prevent authentication before startup has completed

Ben Peter created SLING-3119: Summary: Startup Filter: move to HTTP filter to prevent authentication before startup has completed Key: SLING-3119 URL: https://issues.apache.org/jira/browse/SLING-3119

[jira] [Created] (SLING-2911) Wrong explanation of filter order based on service.ranking

Ben Peter created SLING-2911: Summary: Wrong explanation of filter order based on service.ranking Key: SLING-2911 URL: https://issues.apache.org/jira/browse/SLING-2911 Project: Sling Issue Type

[jira] [Updated] (SLING-2730) Allow JSPs to be excluded from compilation in maven-jspc-plugin

[ https://issues.apache.org/jira/browse/SLING-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Peter updated SLING-2730: - Attachment: SLING-2730-take2.patch > Allow JSPs to be excluded from compilation in maven-jspc-plu

[jira] [Commented] (SLING-2730) Allow JSPs to be excluded from compilation in maven-jspc-plugin

[ https://issues.apache.org/jira/browse/SLING-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587202#comment-13587202 ] Ben Peter commented on SLING-2730: -- Sounds good. I'm attaching a patch that i

[jira] [Updated] (SLING-2730) Allow JSPs to be excluded from compilation in maven-jspc-plugin

[ https://issues.apache.org/jira/browse/SLING-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Peter updated SLING-2730: - Attachment: SLING-2730.patch Attaching patch > Allow JSPs to be excluded f

[jira] [Created] (SLING-2730) Allow JSPs to be excluded from compilation in maven-jspc-plugin

Ben Peter created SLING-2730: Summary: Allow JSPs to be excluded from compilation in maven-jspc-plugin Key: SLING-2730 URL: https://issues.apache.org/jira/browse/SLING-2730 Project: Sling Issue

[jira] [Commented] (SLING-2449) background servlets: enable tracking of user, status-code, content-type, length and encoding

[ https://issues.apache.org/jira/browse/SLING-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239405#comment-13239405 ] Ben Peter commented on SLING-2449: -- It would probably make sense to support a la

[jira] [Updated] (SLING-2449) background servlets: enable tracking of user, status-code, content-type, length and encoding

[ https://issues.apache.org/jira/browse/SLING-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Peter updated SLING-2449: - Attachment: SLING-2449_background_servlets__enable_tracking_of_user,_status-code,_content-type

[jira] [Updated] (SLING-2449) background servlets: enable tracking of user, status-code, content-type, length and encoding

[ https://issues.apache.org/jira/browse/SLING-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Peter updated SLING-2449: - Labels: patch (was: ) > background servlets: enable tracking of user, status-code, content-t

[jira] [Created] (SLING-2449) background servlets: enable tracking of user, status-code, content-type, length and encoding

Project: Sling Issue Type: Improvement Components: Extensions Reporter: Ben Peter Enable background jobs to store the user on whose behalf the request was backgrounded Enable background job to store the following data from the result of the backgrounded

[jira] [Commented] (SLING-2156) Provide error handling for POST operations

[ https://issues.apache.org/jira/browse/SLING-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163579#comment-13163579 ] Ben Peter commented on SLING-2156: -- Justin, +1 for your proposed patch. ( line 24

[jira] [Created] (SLING-2240) move org.apache.sling.servlets.post.impl.helper.DateParser to commons

: Wish Components: Commons Affects Versions: Servlets Post 2.1.0 Reporter: Ben Peter DateParser is a nice utility and comes in handy in a lot of cases. As such, it would be great to have it in a place where it is part of an exported package instead of being locked in in the