- From: Hugh Winkler <hughw@wellstorm.com>
- Date: Fri, 18 Aug 2006 23:01:47 -0500
- To: "Booth, David (HP Software - Boston)" <dbooth@hp.com>
- Cc: "Ian Hickson" <ian@hixie.ch>, noah_mendelsohn@us.ibm.com, "Anne van Kesteren" <annevk@opera.com>, www-tag@w3.org
On 8/18/06, Booth, David (HP Software - Boston) <dbooth@hp.com> wrote: > > You raise an important practical point, but I would imagine that the > same tool vendors who are doing it wrong now would again mindlessly add > "authoritative=yes" to their generated headers, regardless of the > document's actual content type. Then, to distinguish that misuse from > really authoritative usage we'd have to add yet another attribute > "really-authoritative=yes". And then the same thing would happen all > over again, and we'd have to add "really-really-authoritative=yes", and > so on. > Well there's really no incentive for a HTTP or app server vendor to do that. Doing so wouldn't improve behavior against browsers, while enabling admins to fine tune their content type authority *would* improve behavior against browsers. Hugh
Received on Saturday, 19 August 2006 04:01:51 UTC