search

rijojoy / chrome-rest-client

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

Chrome's User-Agent is the request #147

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. In header set new User-Agent key-value pair
2. make a call
3. the other side receives Chrome's User-Agent string, not the one that was set.

What is the expected output? What do you see instead?
- I expect, that set User-Agent string will replace Chrome's one.

On what operating system, browser and browser version?
- Win 7; 64bit; Chrome 24.0.1312.52 m;

Original issue reported on code.google.com by Juraj.So...@gmail.com on 22 Jan 2013 at 1:52

GoogleCodeExporter commented 9 years ago 
Chrome's User-Agent in the request

Original comment by Juraj.So...@gmail.com on 22 Jan 2013 at 1:54

GoogleCodeExporter commented 9 years ago

Original comment by Juraj.So...@gmail.com on 22 Jan 2013 at 1:57

Attachments:

GoogleCodeExporter commented 9 years ago 
Setting User-Agent header id prohibited by the spec. It may cause security 
issues and the Chrome Team don't want to allow set this header event for a 
extensions.
However there is an API available for extension which allows extensions to 
modify headers prohibited header. Bad news is this API is in Chrome beta 
channel and it is not available now. As soon as it will be available for stable 
channel you will have possibility to overwrite user-agent and many more 
headers.

Original comment by jarro...@gmail.com on 29 Jan 2013 at 1:20

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

Original comment by jarro...@gmail.com on 27 Mar 2013 at 3:34

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

Original comment by jarro...@gmail.com on 27 Mar 2013 at 3:35

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

Original comment by jarro...@gmail.com on 6 Nov 2013 at 7:15

GoogleCodeExporter commented 9 years ago 
Which version of Chrome allows for header control? What is the process for 
editing those headers?

Original comment by Rob.Isak...@gmail.com on 6 Nov 2013 at 7:44

GoogleCodeExporter commented 9 years ago 
So far only stable channel doesn't have this feature. However I'm implementing 
socket API for new Chrome Apps in ARC app. It's taking some time but I want to 
upgrade the app before end of this month. Then You'll be able to set any kind 
of header.

Original comment by jarro...@gmail.com on 6 Nov 2013 at 7:49

GoogleCodeExporter commented 9 years ago 
It has been a few months. Other chrome web apps 
(https://chrome.google.com/webstore/detail/dev-http-client/aejoelaoggembcahagimd
iliamlcdmfm?hl=en) support Referer, but it still doesn't work in ARC. Any 
thoughts on when it will be ready?

Original comment by Rob.Isak...@gmail.com on 2 May 2014 at 9:57