- From: Cameron Heavon-Jones <cmhjones@gmail.com>
- Date: Tue, 5 Apr 2011 17:54:30 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: mike amundsen <mamund@yahoo.com>, public-html@w3.org
On 05/04/2011, at 5:40 PM, Julian Reschke wrote: > On 05.04.2011 18:35, Cameron Heavon-Jones wrote: >> ... >>>> In the example of a combined agent (i'm thinking in the same vein of the old netscape navigator?) wouldn't the different functional contexts define different requests? >>>> >>>> Why would a WebDAV service initiate a request with "Accept: text/html" if it doesn't want html? >>> >>> Unlikely on purpose, but there's a risk that they may be sending a default because they don't care. >> >> Ok, i think that's a different case then. If a UA is sending Accept that, as far as the service is concerned, it shouldn't be, then it should be given the response which is suitable for that UA. In the case of WebDAV, default to text/plain with a status message. > > How do you intend to detect what kind of UA is doing the request? I think the User-Agent header has to be used...there is no other means i am aware of. The case we are talking about too isn't browsers but WebDAV or some badly behaved automated agent and as a means of corrective-behaviour not standards. > >> This amounts to recommending UA-sniffing, but in the case of UAs that "don't care" i think this is a measured response. > > Eek. In order to provide services for the future, concessions have to be made for the past... > >>> Also, absence of "Accept:" implies "accepts anything", so you wouldn't be able to do conneg by the spec. >> >> This is ok...the default for a UA which accepts anything can be to provide nothing - or just the text/plain message response. > > Not convinced :-) yeah, all i'm saying is that the default response doesn't have to be html.
Received on Tuesday, 5 April 2011 16:55:00 UTC