search

orbednetwork / chrome-rest-client

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

Host Header not Sent #194

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a GET request against localhost:8080
2. Set text field headers as follows:
Host: headlines.api.com
Accept: application/json
3. Observe the following headers on the request:
Accept: application/json
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Chrome/28.0.1500.45 Safari/537.36
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8

What is the expected output? What do you see instead?
I'd expect the Host header to be included in the Headers listed in the request. 
 I'd expect that Header to correspondingly be sent to the specified endpoint.

On what operating system, browser and browser version?
Debian 7 (Wheezy)
Chrome Version 28.0.1500.45

I **believe** I replicated this on my Windows system yesterday, but am not in 
front of it to confirm.

Please provide any additional information below.
I'm able to verify that I can make a curl request against the given interface 
and get back my expected behavior:
curl -H "Host: headlines.api.com" http://localhost:8080/headlines/9484844

I'm not sure if this is the fault of the rest client, or something else 
downstream.  However, the curl makes me feel this should be functional.

Thanks

Original issue reported on code.google.com by scannell...@gmail.com on 2 Aug 2013 at 8:26

GoogleCodeExporter commented 9 years ago 
It is the same case.

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