Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 450EC97EE for ; Tue, 24 Jul 2012 16:38:08 +0000 (UTC) Received: (qmail 60807 invoked by uid 500); 24 Jul 2012 16:38:07 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 60774 invoked by uid 500); 24 Jul 2012 16:38:07 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 60759 invoked by uid 99); 24 Jul 2012 16:38:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2012 16:38:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of subwiz@gmail.com designates 209.85.161.179 as permitted sender) Received: from [209.85.161.179] (HELO mail-gg0-f179.google.com) (209.85.161.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2012 16:38:00 +0000 Received: by ggnk3 with SMTP id k3so6165279ggn.10 for ; Tue, 24 Jul 2012 09:37:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=dR+vSCCAqjgGSIDI9fYL3xQF8/zDGHalWTTot9qDOI8=; b=gLC6Y97PK8+3J7U0BRpALSBN7Frov8qcgeYJLfvnV156VeD/lbtsGjCZJnn6cbk/bj kNE+CIPuW4TsPagl6VgNpaV7Q2Ak3BTwNx5cxdd2ruvTSK6WfFTPfaPxssosKuUb9Yra cS9C3sovPoiFsLuARhs+Of5PydmJaVXUncKg+LYbRpVPrUzagzwVtHjpcsAZ9qaXpO8w gH1BonfNN4FXBeooOqOVzC3jS/uuNH+40M/YbRgkZaO2Xn0zQy1N1E8shN9zQKf1odks RlcLutfGvjMBeZr1kT01ZykCXWUd01aCWHoMIrJ0PQMui8dXlQwQImwx9bEa1Y2lvoPo yo7Q== MIME-Version: 1.0 Received: by 10.42.163.4 with SMTP id a4mr16659699icy.27.1343147859762; Tue, 24 Jul 2012 09:37:39 -0700 (PDT) Received: by 10.64.47.202 with HTTP; Tue, 24 Jul 2012 09:37:39 -0700 (PDT) Date: Tue, 24 Jul 2012 12:37:39 -0400 Message-ID: Subject: Entity body for delete From: Subhash Chandran To: HttpClient User Discussion Content-Type: multipart/alternative; boundary=90e6ba6e8cfe0fdd6d04c595fb52 --90e6ba6e8cfe0fdd6d04c595fb52 Content-Type: text/plain; charset=UTF-8 Hi, As per the discussion below, the spec seems to support Entity body for Delete: http://stackoverflow.com/questions/299628/is-an-entity-body-allowed-for-an-http-delete-request Is there any plans of supporting Entity body for Delete in HTTPClient? -- Regards, Subhash Chandran S http://code.google.com/p/rest-client/issues/detail?id=147 --90e6ba6e8cfe0fdd6d04c595fb52--