search

orbednetwork / chrome-rest-client

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

Allow customizable Origin header #205

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I would like to specify a custom Origin header in the request, instead of using 
the default "chrome-extension://blablabla" value all the time. This would be 
useful when testing with CORS-compliant servers that only allow a specific 
domain or list of domains.

What steps will reproduce the problem?
1. Create a POST request to a CORS-compliant service
2. Specify the desired Origin header in the headers list
3. Execute the request

What is the expected output? What do you see instead?
The provided Origin header is ignore and the default value 
"chrome-extension://blablablabla" is used instead.

On what operating system, browser and browser version?
Windows 7, Chrome latest

Original issue reported on code.google.com by benjamin...@gmail.com on 9 Sep 2013 at 8:31

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago 
I believe This was not a duplicate. of #62. Is the User-Agent header related to 
CORS?

Original comment by brunoabdon on 5 May 2015 at 2:39