- From: Rob Manson <roBman@mob-labs.com>
- Date: Wed, 5 Sep 2012 14:20:50 +1000
- To: public-webapps@w3.org
+1 roBman On Wed, 5 Sep 2012 14:03:35 +1000 Mark Nottingham <mnot@mnot.net> wrote: > The current draft of XHR2 doesn't allow clients to set the UA header. > > 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. > > I understand that it may not be desirable to allow UA to be > overwritten, but making it append-only would be valuable... > > Cheers, > > > -- > Mark Nottingham http://www.mnot.net/
Received on Wednesday, 5 September 2012 04:21:08 UTC