search

Vaishalirajput / chrome-rest-client

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

Request headers incorrect #267

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
When I make a call from ARC, request headers are present that I don't expect. I 
am also unable to change some of the request headers. For example, in some 
requests I would like to change the User-Agent, but this is always changed back 
to Chrome's default setting. I would also like to send some requests without 
cookies, but any existing cookies are always sent.

What steps will reproduce the problem?
1. Open Advanced Rest Client (ARC)
2. Provide any URL
3. Leave Headers empty
4. Make a request

1. Open ARC
2. Provide any URL
3. Add a header to overwrite User-Agent
4. Send the request

What is the expected output? What do you see instead?
I would expect the request to be sent with no headers, since I left the headers 
deliberately empty. Instead It adds headers.

I would expect any explicit headers to be sent with the request. Instead they 
are modified by Chrome before being sent.

On what operating system, browser and browser version?
Windows 7 Pro, latest chrome and ARC.

Original issue reported on code.google.com by dwmaill...@gmail.com on 21 Aug 2014 at 5:51

GoogleCodeExporter commented 8 years ago 
Some headers are set by the browser (or rather XmlHttpRequest object 
implementation) and can't be overridden. I'm working on chrome's sockets.api to 
workaround this limitation but implementation HTTP protocol in javascript takes 
a time. 
To finish the work I'm waiting until Chrome Team will implement SSL connections 
on sockets API so the app will be able to use SSL.

Original comment by jarro...@gmail.com on 22 Sep 2014 at 3:15