- From: Joel N. Weber II <devnull@gnu.ai.mit.edu>
- Date: Wed, 4 Jun 1997 19:20:30 -0400
- To: koen@win.tue.nl
- Cc: masinter@parc.xerox.com, dwm@xpasc.com, http-wg@cuckoo.hpl.hp.com
From: koen@win.tue.nl (Koen Holtman)
Date: Wed, 4 Jun 1997 23:39:10 +0200 (MET DST)
Here is the problem I think we were solving:
Problem: The HTTP/1.x negotiation infrastructure (Accept headers,
User-Agent header, Vary) is not good enough.
At the core, it is really as simple as that. Can we agree on this
problem description?
What makes the negotiation infrastructure not good enough?
How about this:
Although the HTTP/1.x Accept headers provide a method for finding
out the media types supported by a user agent, they do not provide
a method for finding out which HTML features are supported by
a user agent. Servers often want to provide differing content
depending on whether or not the client supports features such
as frames, client-side scripting, etc. A more fine-grained
method of describing the HTML capabilities needs to be defined.
Received on Wednesday, 4 June 1997 16:23:14 UTC