[scim] Clarification on body request for DELETE
Alexandre Santos <asantos@pingidentity.com> Wed, 27 March 2013 16:04 UTC
Return-Path: <asantos@pingidentity.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB38521F8629 for <scim@ietfa.amsl.com>; Wed, 27 Mar 2013 09:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.976
X-Spam-Level:
X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z+nhun7BpjeJ for <scim@ietfa.amsl.com>; Wed, 27 Mar 2013 09:04:36 -0700 (PDT)
Received: from na3sys009aog117.obsmtp.com (na3sys009aog117.obsmtp.com [74.125.149.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7710C21F918F for <scim@ietf.org>; Wed, 27 Mar 2013 09:04:35 -0700 (PDT)
Received: from mail-we0-f198.google.com ([74.125.82.198]) (using TLSv1) by na3sys009aob117.postini.com ([74.125.148.12]) with SMTP ID DSNKUVMYigBN4tzWBrOIXweERliXOYN5+3X/@postini.com; Wed, 27 Mar 2013 09:04:35 PDT
Received: by mail-we0-f198.google.com with SMTP id k14so7493021wer.1 for <scim@ietf.org>; Wed, 27 Mar 2013 09:04:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=TAep4OZ+384/gFbtF8y9SZy0IUlWz1OIMos25dwJFN8=; b=oVtOyMbJyIHa9uTDs/kfYZS/zEeGUx9WhAmeIq4++1IsG9Y/2Pw6mGbdhlEmkdjKiA kG7zHTu3lNxFvrsRhhXg9e5LsVqCrw7tez2/eYfZcRvxTrIyo2Ge1FyDpluX8VGBNn9u EkfA1XTsofWDvRFu0JKIYOL70M/RC6oSmvoxy2yKu4O4t8lkop8YBW0kziZAP0k68Itz FqhlYrUAqGQw7R2jdn78M4v1+a0I0GEA5WecjgDzqr+odldrWHzGIRuN2lw/lvE5JHcH LfNbzFOYQZ7ouMqVpCdoRYzRTw5U1gtL+RPJ1niiVXAsgxvnY8mL2nrt35+hlbHABErq Tt9g==
X-Received: by 10.180.77.226 with SMTP id v2mr10578089wiw.33.1364400252672; Wed, 27 Mar 2013 09:04:12 -0700 (PDT)
X-Received: by 10.180.77.226 with SMTP id v2mr10577748wiw.33.1364400249689; Wed, 27 Mar 2013 09:04:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.152.226 with HTTP; Wed, 27 Mar 2013 09:03:49 -0700 (PDT)
From: Alexandre Santos <asantos@pingidentity.com>
Date: Wed, 27 Mar 2013 09:03:49 -0700
Message-ID: <CAPx6tN7x1MS+W=rbXF1c9p2qepJN3pco+h6MQYXmGHJakF+3Vw@mail.gmail.com>
To: scim@ietf.org
Content-Type: multipart/alternative; boundary="f46d043c7f1a36fbdf04d8ea30b7"
X-Gm-Message-State: ALoCoQlBgusqvx02W1H+B76+GzQvFcmgPfS7NhuqskcyzXMsZq6zsn29B80ep20nQmkguHKOOY4ZuvZjDXsYhdq/Yb3GxghX8JEefeRKF5zSfXBjs/3oKm9EamOnyq+jb59Zx5jTAB+g
Subject: [scim] Clarification on body request for DELETE
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/scim>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2013 16:04:36 -0000
The spec for PUT says "3.3.1... Unless otherwise specified a successful PUT operation returns a 200 OK response code and the entire Resource within the response body" For POST: "3.1... the response body MUST contain the newly created Resource." For DELETES it says " 3.4. Deleting Resources Consumers request Resource removal via DELETE. Service Providers MAY choose not to permanently delete the Resource, but MUST return a 404 error code for all operations associated with the previously deleted Id. Service Providers MUST also omit the Resource from future query results. In addition the Service Provider MUST not consider the deleted resource in conflict calculation. For example if a User resource is deleted, a CREATE request for a User resource with the same userName as the previously deleted resource should not fail with a 409 error due to userName conflict. " My question is, what (if anything at all) should be returned in the response body as a result of a successful DELETE operation. Thanks, Alex Santos * *
- [scim] Clarification on body request for DELETE Alexandre Santos
- Re: [scim] Clarification on body request for DELE… Kelly Grizzle
- Re: [scim] Clarification on body request for DELE… Phil Hunt
- Re: [scim] Clarification on body request for DELE… Phil Hunt
- Re: [scim] Clarification on body request for DELE… Kelly Grizzle
- Re: [scim] Clarification on body request for DELE… Shelley
- Re: [scim] Clarification on body request for DELE… Erik Wahlström
- Re: [scim] Clarification on body request for DELE… Shelley