Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call)

Mykyta Yevstifeyev <evnikita2@gmail.com> Thu, 16 December 2010 15:58 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDA1A3A6902 for <ietf@core3.amsl.com>; Thu, 16 Dec 2010 07:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.071
X-Spam-Level:
X-Spam-Status: No, score=-2.071 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MEWNZGKhAX-r for <ietf@core3.amsl.com>; Thu, 16 Dec 2010 07:58:17 -0800 (PST)
Received: from mail-bw0-f51.google.com (mail-bw0-f51.google.com [209.85.214.51]) by core3.amsl.com (Postfix) with ESMTP id 4455A3A68DC for <ietf@ietf.org>; Thu, 16 Dec 2010 07:58:10 -0800 (PST)
Received: by bwz8 with SMTP id 8so3890360bwz.38 for <ietf@ietf.org>; Thu, 16 Dec 2010 07:59:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=KBNWOY+Z7x/q5QrfQdgHYB2IsorOgTqumox/TzssJWo=; b=vdQOmEkxgVONEf3RtXjXMKE02i1iTq4RwT9Vi07kxSj1bANExsKB103f2MpjFym6/C HvxSuSOni3IOPdtkc62a3iUoThJ+W0K4FblM92ae+rTlWwgMQMtGrlo27ew7OwBvXaUA s26nPJOHw+ql45YgeEm4e9LdS1BLRHH/pSW0c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=axIIoA+SFZ0tx9U6uSz0rNVHuxWapNZS9vZbKzSXJhXvxpxbNEZvR8o5b4ojDK6N/E j1c7h+V8SKx3oYDKS1WPQzWZGx5N/cTCQp5q8kq+zEMK11leDGG8zsEGQCaIw3E6kaFk k3umVa5yx1es+ASrdsQ5zcuHhGGsPtI0EAah8=
Received: by 10.204.118.7 with SMTP id t7mr8661517bkq.87.1292515194489; Thu, 16 Dec 2010 07:59:54 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id j11sm1362240bka.12.2010.12.16.07.59.51 (version=SSLv3 cipher=RC4-MD5); Thu, 16 Dec 2010 07:59:53 -0800 (PST)
Message-ID: <4D0A3783.1050801@gmail.com>
Date: Thu, 16 Dec 2010 18:00:03 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Daniel Stenberg <daniel@haxx.se>
Subject: Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call)
References: <4D08FF55.1040802@gmail.com> <alpine.DEB.2.00.1012152203070.29000@tvnag.unkk.fr> <AANLkTimLjX7EiUFSLnk1==UKckzWZ8Sq0CNXkfSOz9Bj@mail.gmail.com> <alpine.DEB.2.00.1012161117170.2325@tvnag.unkk.fr> <4D0A28DE.40105@gmail.com> <alpine.DEB.2.00.1012161635480.31573@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1012161635480.31573@tvnag.unkk.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, httpbis Group <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Dec 2010 15:58:17 -0000

Daniel,

I'll now explain that. Let A is the host-under-debugging (HUD). There is 
another host, B, which is debugger. Let there is some new HTTP server 
software on A. B's sending requests with different methods, headers and 
entity to test A for appropriate processing of headers. Let B is sending 
the request with header X-Foo, which is to be used or already used 
widely among the Internet. But A does not recognize it. But it is not 
easy for developers to get known this. If discussed header is used, B 
testers can simply analyze A's answer (as it is to be done at all) to 
find out the problem and fix it. That is debugging purpose, IMO.

Hope I explained everything clearly.

Any suggestions are welcome.

All the best,
Mykyta Yevstifeyev

16.12.2010 17:46, Daniel Stenberg wrote:
> On Thu, 16 Dec 2010, Mykyta Yevstifeyev wrote:
>
>> Daniel,
>>
>> You may find some related discussions on
>>
>> http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/
>>
>> dated from Monday, 22 November 2010 and Tuesday, 23 November 2010
>
> Thanks.
>
> The only tiny piece of explanation I can find there is 
> http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0493.html 
> where you say "But aren't debugging purposes a weighty argument?".
>
> Does this mean that debugging HTTP clients(?) and servers(?) is your 
> primary purpose for this feature? In what way does this help you debug?
>
> I've been developing (and debugging) HTTP clients for over a decade 
> and I've not missed this header. I'm genuinely trying to understand 
> the use case and what benefit this header is to bring for that 
> purpose, so that I can read the draft with that in mind.
>
> So please, even if this is repeating something you've expressed 
> before, can you enlighten us (again) exactly in what ways you intend 
> to use this header/feature?
>
> (If someone else have any good suggestions, that'll do fine as well!)
>