IETF Logo Mail Archive

Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC

Mykyta Yevstifeyev <evnikita2@gmail.com> Fri, 17 December 2010 14:31 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 B0D1A3A6B62 for <ietf@core3.amsl.com>; Fri, 17 Dec 2010 06:31:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.244
X-Spam-Level:
X-Spam-Status: No, score=-3.244 tagged_above=-999 required=5 tests=[AWL=0.355, BAYES_00=-2.599, 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 PPChIE8x2toE for <ietf@core3.amsl.com>; Fri, 17 Dec 2010 06:31:25 -0800 (PST)
Received: from mail-bw0-f50.google.com (mail-bw0-f50.google.com [209.85.214.50]) by core3.amsl.com (Postfix) with ESMTP id A374E3A6B55 for <ietf@ietf.org>; Fri, 17 Dec 2010 06:31:24 -0800 (PST)
Received: by bwg12 with SMTP id 12so935125bwg.37 for <ietf@ietf.org>; Fri, 17 Dec 2010 06:33:11 -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=cfLFFv4YUP/slLBNaDNuqKK9ThHqWoKmPmmZBKo+HP8=; b=mxz6JEEZsEJea8750Jjzog0+x1jPVHuvSC6/Zg0LrFXzvv4iKwnRvPnObqoLtv4yyq D4T4ST/Iz86yt1bTzx+fD3miO6ekih5oFRpIHKcm8G2DXQdBhYTQ67iM54xQlWqe5opZ /AFlPvs5JWJmUyilSoFhY6jS8T2FtqjWV7tek=
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=ngqsrd0WiJCU3TQd8WLnN8Wz5gt8Q0kovEQI1KKGB90CiagqTGyyXpimNfclXFRDGn ngiAtD8IFFC6y8djp6CX8kxAu9bEr/p9ZDwt6cdorC8+slZac4CxFO/0wjOJzPRAuHvI qKH8+T2YtmZgoFoQrHf4Jl8sp1PwfwLbNCNlo=
Received: by 10.204.68.13 with SMTP id t13mr625491bki.164.1292596390944; Fri, 17 Dec 2010 06:33:10 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id s14sm1641667bkb.4.2010.12.17.06.33.08 (version=SSLv3 cipher=RC4-MD5); Fri, 17 Dec 2010 06:33:10 -0800 (PST)
Message-ID: <4D0B74AF.9080102@gmail.com>
Date: Fri, 17 Dec 2010 16:33:19 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC
References: <20101213132808.2379.30041.idtracker@localhost> <6.2.5.6.2.20101217021213.0c3125b0@resistor.net> <4D0B6B6D.7040001@gmail.com> <alpine.DEB.2.00.1012171458260.28703@tvnag.unkk.fr> <4D0B71AA.5060305@gmail.com> <4D0B73BA.9060909@gmx.de>
In-Reply-To: <4D0B73BA.9060909@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, ietf@ietf.org, Daniel Stenberg <daniel@haxx.se>, 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: Fri, 17 Dec 2010 14:31:25 -0000

17.12.2010 16:29, Julian Reschke wrote:
> On 17.12.2010 15:20, Mykyta Yevstifeyev wrote:
>> ...
>> In previous version there have been the 'server' and 'client' terms
>> instead 'host'. However it is obvious for me that there can be as
>> servers as clients that do not recognize some headers of another side of
>> exchange.
>> ...
>
> But clients can't respond with the header, so there's no point in 
> pretending this applies to them.
In my document the term 'header' means 'header field' since client are 
able to put any header to the request and I meant just it.

Mykyta
>
>> ...
>
> Best regards, Julian
>

v2.23.0 | Report a Bug | By Email