- From: Robin Berjon <robin@w3.org>
- Date: Wed, 05 Sep 2012 12:33:28 +0200
- To: Mark Nottingham <mnot@mnot.net>
- CC: public-webapps@w3.org
On 05/09/2012 06:03 , Mark Nottingham wrote: > That's unfortunate, because part of the intent of the UA header is to identify the software making the request, for debugging / tracing purposes. > > Given that lots of libraries generate XHR requests, it would be natural for them to identify themselves in UA, by appending a token to the browser's UA (the header is a list of product tokens). As it is, they have to use a separate header. Do you have a use case that does not involve the vanity of the library's authors? :) -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Thursday, 6 September 2012 07:35:42 UTC