Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5DB9D200C42 for ; Fri, 10 Mar 2017 09:43:17 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5C992160B69; Fri, 10 Mar 2017 08:43:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A8415160B79 for ; Fri, 10 Mar 2017 09:43:16 +0100 (CET) Received: (qmail 15442 invoked by uid 500); 10 Mar 2017 08:43:15 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 15410 invoked by uid 99); 10 Mar 2017 08:43:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Mar 2017 08:43:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5A5D2C0912 for ; Fri, 10 Mar 2017 08:43:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id WFT55Wjb8Mv3 for ; Fri, 10 Mar 2017 08:43:14 +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 3E9DA5F1EE for ; Fri, 10 Mar 2017 08:43:14 +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 EEEC8E0A31 for ; Fri, 10 Mar 2017 08:43:09 +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 56F69243B6 for ; Fri, 10 Mar 2017 08:43:09 +0000 (UTC) Date: Fri, 10 Mar 2017 08:43:09 +0000 (UTC) From: "Julian Reschke (JIRA)" To: dev@hc.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HTTPCLIENT-1828) HttpDelete does not extend HttpEntityEnclosingRequestBase MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 10 Mar 2017 08:43:17 -0000 [ https://issues.apache.org/jira/browse/HTTPCLIENT-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904727#comment-15904727 ] Julian Reschke commented on HTTPCLIENT-1828: -------------------------------------------- bq. You are very welcome to have a different opinion but a simple, irrefutable fact is that HttpClient 4.x has been built to conform to RFC 2616. It makes no sense to make it partially compliant with RFC723x in some areas and non-complaint in some others. Well, it should be built to conform to HTTP/1.1. Being partially compliant to the newer spec certainly isn't ideal, but nor is it to be compliant to an obsolete spec. bq. And what makes absolutely no sense of what so ever is DELETE and GET with enclosed entity. I agree that it shouldn't be used. The question is whether the HTTP client library should enforce this. > HttpDelete does not extend HttpEntityEnclosingRequestBase > --------------------------------------------------------- > > Key: HTTPCLIENT-1828 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1828 > Project: HttpComponents HttpClient > Issue Type: Improvement > Affects Versions: 4.5.1, 4.5.2, 4.5.3 > Reporter: Saravanakumar Selvaraj > Fix For: 4.5.4, 5.0 Alpha1 > > > Sending body in DELETE is allowed as the HTTP 1.1 specification does not forbid. Hence HttpDelete.class should extend from HttpEntityEnclosingRequestBase instead of HttpRequestBase. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org