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

Re: NEW ISSUE: repeating non-list-type-headers

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 21 Nov 2007 17:32:04 +0100
To: Geoffrey Sneddon <foolistbar@googlemail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <csm8k3laa988g5foumujned15517qq0m9q@hive.bjoern.hoehrmann.de>

* Geoffrey Sneddon wrote:
>On 20 Nov 2007, at 21:54, Henrik Nordstrom wrote:
>
>> It's up to the implementer omho. Implementation detail on how to  
>> behave when seeing things outside specifications.
>
>I strongly disagree — as an implementer, I want to be able to  
>implement HTTP in such a way that it works in the real world (which,  
>in places, relies on totally unspecified behaviour found in browsers)  
>by just reading the spec. If RFC2616bis doesn't address this, other  
>documentation on this will likely appear scattered over the web  
>outwith the HTTP spec. If I cannot just implement HTTP from the spec  
>in such a way that is interoperable with real-world servers, then IMHO  
>the spec is too vague and I have to waste my time reverse-engineering  
>other implementations (likely still not in a way 100% interoperable  
>with real-world servers).

There is no contradiction. You can leave this up to implementers and
point out real-world problems and how they might be addressed at the
same time. Further, while you might want suggestions for implementing
a "web browser", others might want suggestions for implementing some
web service client, and there may well be differences. Documentation
on such real world problems would be very welcome, you can easily put
them into a separate draft and publish it alongside the Working Group's
documents.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 21 November 2007 16:32:17 GMT

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