W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

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

From: Daniel Stenberg <daniel@haxx.se>
Date: Thu, 16 Dec 2010 16:46:53 +0100 (CET)
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
cc: IETF Discussion <ietf@ietf.org>, httpbis Group <ietf-http-wg@w3.org>
Message-ID: <alpine.DEB.2.00.1012161635480.31573@tvnag.unkk.fr>
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!)

-- 

  / daniel.haxx.se
Received on Thursday, 16 December 2010 15:47:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:34 GMT