From dev-return-91507-archive-asf-public=cust-asf.ponee.io@sling.apache.org Wed Sep 12 21:22:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 134C8180630 for ; Wed, 12 Sep 2018 21:22:03 +0200 (CEST) Received: (qmail 24271 invoked by uid 500); 12 Sep 2018 19:22:03 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 24260 invoked by uid 99); 12 Sep 2018 19:22:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Sep 2018 19:22:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9663618FE1C for ; Wed, 12 Sep 2018 19:22:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 7xffroLAnUhg for ; Wed, 12 Sep 2018 19:22:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3D3A45F500 for ; Wed, 12 Sep 2018 19:22:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 79469E0047 for ; Wed, 12 Sep 2018 19:22:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1296F2183D for ; Wed, 12 Sep 2018 19:22:00 +0000 (UTC) Date: Wed, 12 Sep 2018 19:22:00 +0000 (UTC) From: "Eric Norman (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SLING-6767) Jackrabbit Usermanager: Allow to detect whether a POST request was treated by the default POST servlet or the jackrabbit.usermanager MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SLING-6767?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1661= 2629#comment-16612629 ]=20 Eric Norman commented on SLING-6767: ------------------------------------ [~rombert] I understand all that, but I think a developer would think about= it differently than an administrator.=C2=A0 A developer likes the flexibil= ity to do lots of stuff from the client to make their life easier, but an a= dministrator may not want the client to have so much "flexibility" in influ= encing how a request is handled on the server side. > Jackrabbit Usermanager: Allow to detect whether a POST request was treate= d by the default POST servlet or the jackrabbit.usermanager > -------------------------------------------------------------------------= ----------------------------------------------------------- > > Key: SLING-6767 > URL: https://issues.apache.org/jira/browse/SLING-6767 > Project: Sling > Issue Type: Improvement > Components: JCR > Reporter: Konrad Windszus > Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.10 > > > Currently it is impossible to tell from the response whether a POST reque= st has been answered by either the Default Sling POST servlet or the Jackra= bbit Usermanager. Both the JSON and the HTML look exactly the same no matte= r, who answered. It should be possible to see from the client-side whether = a request has been treated by one or the other. -- This message was sent by Atlassian JIRA (v7.6.3#76005)