search

rbfang / chrome-rest-client

Automatically exported from code.google.com/p/chrome-rest-client
0 stars 0 forks source link

How do I set the User-Agent #62

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Tried posting 
2. Cannot set User-Agent value
3.
Is there a way to change the User-Agent that is being sent?
I've added a header, but I think this just send two headers.

Original issue reported on code.google.com by jonathan...@gmail.com on 31 May 2012 at 9:36

GoogleCodeExporter commented 9 years ago 
For now it is not possible to overwrite User-Agent header. It is not allowed by 
spec (for XMLHttpRequest).
It will require new permission "webRequest" for application. Then application 
can overwrite this header.
This feature will be available soon (about 1 month...)

Original comment by jarro...@gmail.com on 31 May 2012 at 10:41

GoogleCodeExporter commented 9 years ago 
Excellent, thanks for the program.

Original comment by jonathan...@gmail.com on 1 Jun 2012 at 4:49

GoogleCodeExporter commented 9 years ago 
It is not available, yet. There is way to set "User-Agent" header in request 
but it only works in chrome dev channel and in new version of the application 
witch is not available. As soon as current dev channel becomes stable I will 
update application to new version.

Original comment by jarro...@gmail.com on 15 Aug 2012 at 11:58

GoogleCodeExporter commented 9 years ago 
Hey,
I've already done changes to the code and it working. But unfortunately it 
still working on dev channel only because of new API used. When it becomes 
stable I will  release update to chrome web store. 
Before that API if was impossible to overwrite User-Agent header (and many 
more) for async XMLHttpRequest.

Original comment by jarro...@gmail.com on 21 Aug 2012 at 8:57

GoogleCodeExporter commented 9 years ago

Original comment by jarro...@gmail.com on 21 Aug 2012 at 8:57

GoogleCodeExporter commented 9 years ago 
It is fixed in revision 127. It will be available in next update.

Original comment by jarro...@gmail.com on 27 Sep 2012 at 3:47

GoogleCodeExporter commented 9 years ago 
Is this feature currently implemented? I've added a custom header, with field 
"User-Agent", but in the Request Headers section it seems to use my browser 
still. I'm on Chrome 30.0.1599.66 m.

Original comment by crumm...@gmail.com on 7 Oct 2013 at 6:31

GoogleCodeExporter commented 9 years ago 
It is still unavailable for Chrome Stable channel. However I already started 
working on new implementation on sockets. It is available for all channels but 
require from me to implement HTTP protocol by myself so it will take a while.

Original comment by jarro...@gmail.com on 9 Oct 2013 at 7:31

GoogleCodeExporter commented 9 years ago 
Issue 209 has been merged into this issue.

Original comment by jarro...@gmail.com on 14 Oct 2013 at 1:41

GoogleCodeExporter commented 9 years ago 
Issue 194 has been merged into this issue.

Original comment by jarro...@gmail.com on 14 Oct 2013 at 1:43

GoogleCodeExporter commented 9 years ago 
Issue 205 has been merged into this issue.

Original comment by jarro...@gmail.com on 14 Oct 2013 at 1:43