IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Fri, 17 December 2010 14:58 UTC

Return-Path: <julian.reschke@gmx.de>
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 10F1F3A6AF2 for <ietf@core3.amsl.com>; Fri, 17 Dec 2010 06:58:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.671
X-Spam-Level:
X-Spam-Status: No, score=-104.671 tagged_above=-999 required=5 tests=[AWL=-2.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 YFxtuw2WXPtQ for <ietf@core3.amsl.com>; Fri, 17 Dec 2010 06:58:51 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id DBF4C3A6AEE for <ietf@ietf.org>; Fri, 17 Dec 2010 06:58:50 -0800 (PST)
Received: (qmail invoked by alias); 17 Dec 2010 15:00:36 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp066) with SMTP; 17 Dec 2010 16:00:36 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19ID7EtA91Ip4FYVKYH/6LAgxVCISsnxIZGQspPNW WDd+OWZ7ytMFtp
Message-ID: <4D0B7B0D.7050105@gmx.de>
Date: Fri, 17 Dec 2010 16:00:29 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
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> <4D0B74AF.9080102@gmail.com>
In-Reply-To: <4D0B74AF.9080102@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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:58:52 -0000

On 17.12.2010 15:33, Mykyta Yevstifeyev wrote:
> 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.

I realize that you use "header" as synonym for "header field".

What I was trying to say was that it doesn't make sense to speak of 
clients and servers in general, when it's really only the server who can 
set the H-N-R header field.

Best regards, Julian

v2.23.0 | Report a Bug | By Email