[jira] [Resolved] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5831. - Resolution: Fixed > Support different thread pools for scheduled tasks >

[jira] [Resolved] (SLING-5873) Update commons compiler to 2.3.0

[ https://issues.apache.org/jira/browse/SLING-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5873. - Resolution: Fixed Updated in 1753446 > Update commons compiler to 2.3.0 >

[jira] [Commented] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385374#comment-15385374 ] Chetan Mehrotra commented on SLING-5831: Fine with me! > Support different thread pools for

[jira] [Created] (SLING-5873) Update commons compiler to 2.3.0

Carsten Ziegeler created SLING-5873: --- Summary: Update commons compiler to 2.3.0 Key: SLING-5873 URL: https://issues.apache.org/jira/browse/SLING-5873 Project: Sling Issue Type: Improvement

Re: [VOTE] Release Apache Sling Parent POM 27

+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

[jira] [Commented] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385366#comment-15385366 ] Carsten Ziegeler commented on SLING-5831: - If removeJob did not throw in previous versions, this

[jira] [Commented] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385355#comment-15385355 ] Chetan Mehrotra commented on SLING-5831: bq. For removeJob(), the API states that a

[VOTE] Release Apache Sling Parent POM 27

Hi, We solved 21 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12334592 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1481 You can use this UNIX script to download the release and verify the signatures:

Re: [DISCUSS] Path filtering support for ResourceChangeListeners

> what about option 2 + 4 together (but only implementiong 'glob' currently)? > > then it would be: > - easy to detect if the user wishs to use a pattern instead of a fixed path > by looking for a prefix (currently this is done by magically looking for > special characters) > - possible to add

[jira] [Comment Edited] (SLING-5742) Do not allow registration of agents/exporters/importers with duplicate names

[ https://issues.apache.org/jira/browse/SLING-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384870#comment-15384870 ] Timothee Maret edited comment on SLING-5742 at 7/19/16 9:17 PM: This issue

[jira] [Commented] (SLING-5742) Do not allow registration of agents/exporters/importers with duplicate names

[ https://issues.apache.org/jira/browse/SLING-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384870#comment-15384870 ] Timothee Maret commented on SLING-5742: --- This issue relates to SLING-5872, however its scope

[jira] [Updated] (SLING-5742) Do not allow registration of agents/exporters/importers with duplicate names

[ https://issues.apache.org/jira/browse/SLING-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-5742: -- Assignee: (was: Timothee Maret) > Do not allow registration of agents/exporters/importers

[jira] [Created] (SLING-5872) Management of agent configurations must identify configurations by name

Timothee Maret created SLING-5872: - Summary: Management of agent configurations must identify configurations by name Key: SLING-5872 URL: https://issues.apache.org/jira/browse/SLING-5872 Project:

Re: [DISCUSS] Path filtering support for ResourceChangeListeners

On 16.7.16 5:56 , Carsten Ziegeler wrote: I wouldn't go with more powerful matching as the idea of the RCLs is that the filter matching is done by the underlying storage provider, e.g. Oak. This allows to delegate the heavy work to the storage and reduce the number of events send by the

[jira] [Resolved] (SLING-5871) osgi-mock: Update to org.apache.felix.scr 2.0.4

[ https://issues.apache.org/jira/browse/SLING-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-5871. --- Resolution: Fixed Completed: At revision: 1753418 > osgi-mock: Update to

[jira] [Updated] (SLING-5871) osgi-mock: Update to org.apache.felix.scr 2.0.4

[ https://issues.apache.org/jira/browse/SLING-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-5871: -- Affects Version/s: Testing OSGi Mock 2.0.4 Fix Version/s: Testing OSGi Mock 2.0.6 >

[jira] [Created] (SLING-5871) osgi-mock: Update to org.apache.felix.scr 2.0.4

Stefan Seifert created SLING-5871: - Summary: osgi-mock: Update to org.apache.felix.scr 2.0.4 Key: SLING-5871 URL: https://issues.apache.org/jira/browse/SLING-5871 Project: Sling Issue Type:

[jira] [Assigned] (SLING-5742) Do not allow registration of agents/exporters/importers with duplicate names

[ https://issues.apache.org/jira/browse/SLING-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret reassigned SLING-5742: - Assignee: Timothee Maret > Do not allow registration of agents/exporters/importers with

RE: [DISCUSS] Path filtering support for ResourceChangeListeners

On Tuesday 19 July 2016 17:05:09 Stefan Seifert wrote: > what about option 2 + 4 together (but only implementiong 'glob' currently)? > > then it would be: > - easy to detect if the user wishs to use a pattern instead of a fixed path > by looking for a prefix (currently this is done by magically

RE: [DISCUSS] Path filtering support for ResourceChangeListeners

what about option 2 + 4 together (but only implementiong 'glob' currently)? then it would be: - easy to detect if the user wishs to use a pattern instead of a fixed path by looking for a prefix (currently this is done by magically looking for special characters) - possible to add regex or other

New module Sling Testing PaxExam

hi all, I've added a new module org.apache.sling.testing.paxexam in trunk/testing recently. It provides Sling's Launchpad Karaf Features as Options for Pax Exam (without Karaf) to setup a Sling instance with less boilerplate code: * allows to run ITs in the same module (with the build

Re: [DISCUSS] Path filtering support for ResourceChangeListeners

Hello again, I'd like to reach to a conclusion for this feature and we currently have the following options: 1. use RegEx for these filters, as proposed by Stefan Seifert - we're already using RegEx for Sling Mapping 2. use a limited glob pattern matching, allowing just '**', '*', as proposed by

[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements

[ https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384449#comment-15384449 ] angela commented on SLING-5868: --- see SLING-5792 for pull request > API to define and retrieve login path

[jira] [Commented] (SLING-5795) Allow for adding/removing individual AuthenticationRequirementHolder entries

[ https://issues.apache.org/jira/browse/SLING-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384448#comment-15384448 ] angela commented on SLING-5795: --- see SLING-5792 for pull request > Allow for adding/removing individual

[jira] [Commented] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384395#comment-15384395 ] Oliver Lietz commented on SLING-5870: - A release of Oak Server is overdue but I would like to wait now

[jira] [Commented] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384378#comment-15384378 ] Bertrand Delacretaz commented on SLING-5870: Is that

[jira] [Commented] (SLING-5253) Remove getAdministrativeResourceResolver() from the Sightly engine

[ https://issues.apache.org/jira/browse/SLING-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384347#comment-15384347 ] Radu Cotescu commented on SLING-5253: - Pushed a potential fix in

[jira] [Commented] (SLING-5863) Make the sightly-maven-plugin m2e compatible

[ https://issues.apache.org/jira/browse/SLING-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384341#comment-15384341 ] Robert Munteanu commented on SLING-5863: Applied in https://svn.apache.org/r1753398 > Make the

[jira] [Commented] (SLING-5863) Make the sightly-maven-plugin m2e compatible

[ https://issues.apache.org/jira/browse/SLING-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384323#comment-15384323 ] Robert Munteanu commented on SLING-5863: IIUC the pom errors are reported whenever a mojo fails.

[jira] [Commented] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384321#comment-15384321 ] Robert Munteanu commented on SLING-5870: I've taken a look at both approaches, and I'm still

[jira] [Resolved] (SLING-3471) Add Sling Replication IT for commands

[ https://issues.apache.org/jira/browse/SLING-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-3471. Resolution: Fixed > Add Sling Replication IT for commands >

[jira] [Resolved] (SLING-3470) Add Sling Replication ITs for all the exposed resources

[ https://issues.apache.org/jira/browse/SLING-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-3470. Resolution: Fixed > Add Sling Replication ITs for all the exposed resources >

[jira] [Commented] (SLING-5863) Make the sightly-maven-plugin m2e compatible

[ https://issues.apache.org/jira/browse/SLING-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384260#comment-15384260 ] Radu Cotescu commented on SLING-5863: - I've played with the plugin and really like the way it works in

Re: [sightly] Updating the commons compiler dependency?

> If all the Sightly tests pass I have no problem with this change. > The unit tests pass and the integration tests are run with launchpad 9 which anyway contains the latest compiler. Carsten > Thanks, > Radu > > On Tue, 19 Jul 2016 at 15:42 Bertrand Delacretaz >

Re: [sightly] Updating the commons compiler dependency?

If all the Sightly tests pass I have no problem with this change. Thanks, Radu On Tue, 19 Jul 2016 at 15:42 Bertrand Delacretaz wrote: > On Tue, Jul 19, 2016 at 3:30 PM, Carsten Ziegeler > wrote: > > ...updating the dependency of > >

[jira] [Commented] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384221#comment-15384221 ] Felix Meschberger commented on SLING-5866: -- The most important uses IIRC for a HEAD request is

[jira] [Commented] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384162#comment-15384162 ] Bertrand Delacretaz commented on SLING-5870: FWIW, {{bundles/jcr/it-jackrabbit-oak}} is

Re: [sightly] Updating the commons compiler dependency?

On Tue, Jul 19, 2016 at 3:30 PM, Carsten Ziegeler wrote: > ...updating the dependency of > commons.compiler from 2.0.0 to 2.3.0 solves the problem... I think the Sightly test suite is pretty solid, so if the tests pass after that update I'm +1 on it. -Bertrand

[jira] [Commented] (SLING-920) Sling Jenkins setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384150#comment-15384150 ] Robert Munteanu commented on SLING-920: --- Applied same change to sling-tooling-trunk-1.7 > Sling

Re: [sightly] Updating the commons compiler dependency?

Forgot to mention that another good reason to update the dependency is to use a compiler which is able to handle java 8 compilation correctly. Carsten > Hi, > > currently Sightly core depends on commons.compiler 2.0.0, however this > has some strange dependencies to Eclipse projects and I can't

[sightly] Updating the commons compiler dependency?

Hi, currently Sightly core depends on commons.compiler 2.0.0, however this has some strange dependencies to Eclipse projects and I can't get past these. In particular it seems these dependencies can't be downloaded: org.eclipse:osgi:jar:3.4.3.R34x_v20081215-1030

[jira] [Commented] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384101#comment-15384101 ] Oliver Lietz commented on SLING-5870: - Scripting Thymeleaf runs tests on Oak:

[jira] [Commented] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384087#comment-15384087 ] Carsten Ziegeler commented on SLING-5870: - +1 to move to Oak - I tried it some time ago but failed

[jira] [Commented] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

[ https://issues.apache.org/jira/browse/SLING-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384075#comment-15384075 ] Konrad Windszus commented on SLING-5867: bq... in case of a non-returning response ... the

[jira] [Created] (SLING-5870) Switch event ITs to use Oak

Robert Munteanu created SLING-5870: -- Summary: Switch event ITs to use Oak Key: SLING-5870 URL: https://issues.apache.org/jira/browse/SLING-5870 Project: Sling Issue Type: Improvement

[jira] [Comment Edited] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

[ https://issues.apache.org/jira/browse/SLING-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384075#comment-15384075 ] Konrad Windszus edited comment on SLING-5867 at 7/19/16 12:25 PM: -- bq.

[jira] [Commented] (SLING-5863) Make the sightly-maven-plugin m2e compatible

[ https://issues.apache.org/jira/browse/SLING-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384041#comment-15384041 ] Robert Munteanu commented on SLING-5863: Ugh, I accidentally pushed my changes (

[jira] [Comment Edited] (SLING-5803) FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384037#comment-15384037 ] Robert Munteanu edited comment on SLING-5803 at 7/19/16 12:14 PM: -- I've

[jira] [Commented] (SLING-5803) FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384037#comment-15384037 ] Robert Munteanu commented on SLING-5803: I've {{@Ignore}}d

[jira] [Commented] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

[ https://issues.apache.org/jira/browse/SLING-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384034#comment-15384034 ] Georg Henzler commented on SLING-5867: -- bq. ... in case of a non-returning response ... the health

[jira] [Updated] (SLING-5869) htl doesn't escape '%' character in uri context

[ https://issues.apache.org/jira/browse/SLING-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5869: --- Description: % char in an href will not be escaped by sightly. This will cause an issue in

[jira] [Created] (SLING-5869) htl doesn't escape '%' character in uri context

Nicolas Peltier created SLING-5869: -- Summary: htl doesn't escape '%' character in uri context Key: SLING-5869 URL: https://issues.apache.org/jira/browse/SLING-5869 Project: Sling Issue

[jira] [Assigned] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

[ https://issues.apache.org/jira/browse/SLING-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-5867: -- Assignee: Konrad Windszus > SlingRequestStatusHealthCheck should add timeout support >

[jira] [Updated] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

[ https://issues.apache.org/jira/browse/SLING-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5867: --- Description: Currently {{o.a.s.hc.support.impl.SlingRequestStatusHealthCheck}} just

[jira] [Commented] (SLING-5792) API to manage Authentication Requirement

[ https://issues.apache.org/jira/browse/SLING-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383894#comment-15383894 ] ASF GitHub Bot commented on SLING-5792: --- GitHub user anchela opened a pull request:

[GitHub] sling pull request #153: SLING-5792, SLING-5868, SLING-5795

GitHub user anchela opened a pull request: https://github.com/apache/sling/pull/153 SLING-5792, SLING-5868, SLING-5795 ## SLING-5792: API to manage Authentication Requirement ### Changes - new interface 'AuthenticationRequirement' - implemented by SlingAuthenticator

[jira] [Created] (SLING-5868) API to define and retrieve login path with along with authentication requirements

angela created SLING-5868: - Summary: API to define and retrieve login path with along with authentication requirements Key: SLING-5868 URL: https://issues.apache.org/jira/browse/SLING-5868 Project: Sling

Re: [VOTE] Release Apache Sling HApi - Sling Hypermedia API client-side tools version 1.0.0

Hi Oliver, OK, it makes sense. So I'll drop the release and make it into an OSGi bundle. - Andrei On Sun, Jul 17, 2016 at 9:04 PM Oliver Lietz wrote: > On Friday 15 July 2016 17:36:31 Andrei Dulvac wrote: > > Hi Oliver, > > Hi Andrei, > > > Because it's a client-side

[jira] [Updated] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

[ https://issues.apache.org/jira/browse/SLING-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5867: --- Description: Currently {{o.a.s.hc.support.impl.SlingRequestStatusHealthCheck}} just

[jira] [Commented] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383813#comment-15383813 ] Carsten Ziegeler commented on SLING-5866: - [~anagarwa] I think we can implement the HEAD logic in

[jira] [Commented] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383777#comment-15383777 ] Ankit Agarwal commented on SLING-5866: -- [~cziegeler] in case on HEAD request, instead of sending it

[jira] [Resolved] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-5849. Resolution: Fixed Fix Version/s: Content Distribution 0.2.0 applied Timothee's patch

[GitHub] sling pull request #152: SLING-5849 - Inconsistent event handling between lo...

Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/152 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383706#comment-15383706 ] ASF GitHub Bot commented on SLING-5849: --- Github user asfgit closed the pull request at:

[jira] [Created] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

Konrad Windszus created SLING-5867: -- Summary: SlingRequestStatusHealthCheck should add timeout support Key: SLING-5867 URL: https://issues.apache.org/jira/browse/SLING-5867 Project: Sling

[jira] [Commented] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383677#comment-15383677 ] Carsten Ziegeler commented on SLING-5831: - Thanks for reporting [~chetanm] I've added a null check

[jira] [Commented] (SLING-5685) Upgrade Commons IO to 2.5

[ https://issues.apache.org/jira/browse/SLING-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383667#comment-15383667 ] Konrad Windszus commented on SLING-5685: Ok, I understand. Since this a a test scope dependency

[jira] [Updated] (SLING-5603) Upgrade Commons Lang to 3.4

[ https://issues.apache.org/jira/browse/SLING-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5603: --- Fix Version/s: (was: Health Check Core 1.2.6) > Upgrade Commons Lang to 3.4 >

[jira] [Commented] (SLING-5603) Upgrade Commons Lang to 3.4

[ https://issues.apache.org/jira/browse/SLING-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383663#comment-15383663 ] Konrad Windszus commented on SLING-5603: According to

[jira] [Updated] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Agarwal updated SLING-5866: - Issue Type: Improvement (was: Bug) > DefaultGetServlet obtains input stream for binary even if

[jira] [Commented] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383648#comment-15383648 ] Amit Gupta commented on SLING-5866: --- [~anagarwa] can you propose a patch as well > DefaultGetServlet

[jira] [Commented] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383642#comment-15383642 ] Ankit Agarwal commented on SLING-5866: -- cc: [~cziegeler] [~fmeschbe] [~amitgupt] > DefaultGetServlet

[jira] [Updated] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Agarwal updated SLING-5866: - Description: As per current implementation any HEAD request will be handled by

[jira] [Created] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

Ankit Agarwal created SLING-5866: Summary: DefaultGetServlet obtains input stream for binary even if request is a HEAD Key: SLING-5866 URL: https://issues.apache.org/jira/browse/SLING-5866 Project: