Missing Response headers

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Submit a rest request to any response sending back response headers

What is the expected output? What do you see instead?
Only the HTTP status code + message are displayed when more response headers 
are passed back.

On what operating system?
Win 7

Please provide any additional information below.

Original issue reported on code.google.com by tor...@gmail.com on 8 Nov 2012 at 6:17

[GoogleCodeExporter]

Is there any error message in output console (in chrome inspector)? What kind 
of response you expected to see? Do you know what may cause a problem?

Thanks for issue report.

Original comment by jarro...@gmail.com on 8 Nov 2012 at 8:32

[GoogleCodeExporter]

Same issue on my Mac OS X Chrome browser.
No error listed in the output console.

I would expect at the very least to see all request headers re-listed and all 
of the response headers listed.
Such as 
server → Jetty(6.1.19)
connection → close
cache-control → no-cache
date → Mon, 22 Apr 2013 13:01:20 GMT
access-control-allow-origin → *
content-type → text/plain; charset=utf-8

Original comment by fabre.la...@gmail.com on 22 Apr 2013 at 1:11

[GoogleCodeExporter]

I see this error occur when a query parameter is sent that includes spaces.  
Urlencode the parameter and the headers are visible again.

Original comment by dana.des...@gmail.com on 16 Jul 2013 at 5:47

[GoogleCodeExporter]

Same problem here: Win 7, Chrome Version 30.0.1599.101 m

I am sending authorization HTTP header to the server (with HTTP GET) and expect 
SMSESSION cookie back - can't see it! Makes it a showstopper for me.

Original comment by mgib...@gmail.com on 18 Oct 2013 at 9:02

[GoogleCodeExporter]

Same issue here. The response headers are very important to the flow of our 
REST APIs, so i can't really use this tool without them. I have to flip over to 
a different REST client for many of my requests.

Original comment by edf...@gmail.com on 7 Nov 2013 at 1:45

[GoogleCodeExporter]

SOme headers can't be read in regular XmlHttpResponse because the spec prohibit 
showing them to the user code.It can't be omitted in the way how the app is 
working right now. However I'm working on new approach where the app is using 
low level socket instead of high level XmlHttpRequest wrapper. I should be able 
to introduce new version of the app within a month. 

Original comment by jarro...@gmail.com on 7 Nov 2013 at 2:08

[GoogleCodeExporter]

I am having the same problem with Windows 8.1, Chrome Version 36.0.1985.125 m, 
and cannot receive any response headers when doing a GET or a POST call. I have 
not checked the other calls. I was receiving them as normal until around 15:00 
30/07/2014 then they stopped appearing. I have not amended any settings. The 
headers are not hidden.

Original comment by sian.scu...@googlemail.com on 31 Jul 2014 at 10:00