Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?
Jacob Champion <champion.p@gmail.com> Tue, 14 February 2017 23:27 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9109C1296D4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Feb 2017 15:27:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.002
X-Spam-Level:
X-Spam-Status: No, score=-7.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tENIJ7MuTYCq for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Feb 2017 15:27:23 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B919129581 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 14 Feb 2017 15:27:23 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1cdmTQ-0001Ec-Oy for ietf-http-wg-dist@listhub.w3.org; Tue, 14 Feb 2017 23:25:28 +0000
Resent-Date: Tue, 14 Feb 2017 23:25:28 +0000
Resent-Message-Id: <E1cdmTQ-0001Ec-Oy@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <champion.p@gmail.com>) id 1cdmTM-0001DX-62 for ietf-http-wg@listhub.w3.org; Tue, 14 Feb 2017 23:25:24 +0000
Received: from mail-io0-f172.google.com ([209.85.223.172]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <champion.p@gmail.com>) id 1cdmTG-0001Qy-4Y for ietf-http-wg@w3.org; Tue, 14 Feb 2017 23:25:18 +0000
Received: by mail-io0-f172.google.com with SMTP id l66so78866139ioi.1 for <ietf-http-wg@w3.org>; Tue, 14 Feb 2017 15:24:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=in6ppDEvOcQqyPt56s9Fl/8hzGrZkIByTfz7k1b/Tk4=; b=NsRyNJ/fbttvsElvp9AVMX5Xdmh4GuBqhK6ABwQ4JJ5KUDQJJaQrKFPQbspTI4P4KL fzUXFj1a18o0yGWJwwi9qfPYqb0e1T+IfW5xQJmUnstGOS96Or78F2FsWYgjrSYaVniV JcDYKWhcwQNFjj2NipVrP0dZkdUGZ3gv9WoFoBl4c4qrrxGEQklE4NB6sItJp3rHjXlo g3R22S/IgvXt8GVaBXSXd948xxjwkP1MLk8g+nt5L7ZonVIx//e6tM2/GX4EGYUgQTyq q9bZTtEEkKjf3//oM9me25AZ44SPvZ+yJSc14cuWVybMh2ZTEX30JceCxjqX4qgGKKRF 2qMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=in6ppDEvOcQqyPt56s9Fl/8hzGrZkIByTfz7k1b/Tk4=; b=EO5KAMrl614TAkUEOvAmJRBgh7bj2JHHpmguSbwG8gDQkvgFdTuoJHfYOLacCpw5W9 ld7+Fr2wkcWa0mcQ81dN32MGdW+YHGDc9F657bqJ5axxffLLEH2lxY0Kb4n3jFcNes9k J7C9vYwiB8brp0Khwmx55bghl49jp7NVUVmaHGUVVwOc72svPlpdu1oy7qW4Zgp1q8E2 eqWgwnaT4gmK4P/HbdL6vEaYi7AvvzLwSb4s+Ko6z0gk+vqghyNDRoo130Sklr/Nvlah 1lMn85Csyt+A/EZJfgDRqdjO3Cv/uekR/gqhAfQZV+I195uMVLgwqO2fHNgxd8nv3Y8n hVcA==
X-Gm-Message-State: AMke39lyW/UgDe8mLUCMeKw23bi7BSuZFI0xAY7xqwC5qUcoDL4M0XnK+iiUUef0N0kIXg==
X-Received: by 10.98.32.221 with SMTP id m90mr34586421pfj.127.1487114691186; Tue, 14 Feb 2017 15:24:51 -0800 (PST)
Received: from [192.168.1.2] (50-39-112-180.bvtn.or.frontiernet.net. [50.39.112.180]) by smtp.gmail.com with ESMTPSA id j7sm3182887pfe.84.2017.02.14.15.24.50 for <ietf-http-wg@w3.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 15:24:50 -0800 (PST)
To: ietf-http-wg@w3.org
References: <emdcb96fc0-0d2f-436c-9f1f-05beffe7593e@bodybag> <e01c4945-1116-d258-7004-ea917843bf3d@ninenines.eu> <ema747b801-6dcc-4b2d-ac95-9a027e10c0b4@bodybag> <7874c62b-c6a0-5d84-8115-20016b45118a@measurement-factory.com> <em541e3407-4e99-468e-a1e7-85a7bf074bdd@bodybag> <874938e6-2153-e02a-ab0e-814f468c58f8@measurement-factory.com> <em95b13204-3a33-4bd5-81d2-791e809b9cd2@bodybag>
From: Jacob Champion <champion.p@gmail.com>
Message-ID: <abf8f814-2eb3-87fa-a692-17e5d05313d7@gmail.com>
Date: Tue, 14 Feb 2017 15:24:48 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <em95b13204-3a33-4bd5-81d2-791e809b9cd2@bodybag>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=209.85.223.172; envelope-from=champion.p@gmail.com; helo=mail-io0-f172.google.com
X-W3C-Hub-Spam-Status: No, score=-7.1
X-W3C-Hub-Spam-Report: AWL=0.171, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-3.296, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1cdmTG-0001Qy-4Y 9154e8f717edb67e674648c719f0255e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?
Archived-At: <http://www.w3.org/mid/abf8f814-2eb3-87fa-a692-17e5d05313d7@gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33508
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On 02/14/2017 03:18 PM, Adrien de Croy wrote: > The only true size of a body is what you obtain by counting its bytes. Can you explain how you would count the bytes in a message body if you don't know where that body ends? --Jacob
- Sections 3.3.2 and 3.3.3 allow bogus Content-Leng… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Loïc Hoguin
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Poul-Henning Kamp
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- RE: Sections 3.3.2 and 3.3.3 allow bogus Content-… Mike Bishop
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Matthew Kerwin
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jason T. Greene
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jacob Champion
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Poul-Henning Kamp
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Daniel Stenberg
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Willy Tarreau
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jacob Champion
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jacob Champion
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Matthew Kerwin
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Mark Nottingham
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Willy Tarreau
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Poul-Henning Kamp
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Cory Benfield
- Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Patrick McManus