search

safiresh / chrome-rest-client

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

Header not saving #165

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Save Post service with Header set Content-Type application/json
2. open another saved service
3. open saved post service in 1, Header is not saved ??

What is the expected output? What do you see instead?
I have tried setting the dropdown, and saving in the Header, but neither are 
being saved.
I am overwriting from previously saved request, but other values are being 
stored.

On what operating system, browser and browser version?
OSX 10.8.3 Chrome -  25.0.1364.172

Please provide any additional information below.

Original issue reported on code.google.com by markjwil...@gmail.com on 21 Mar 2013 at 4:32

GoogleCodeExporter commented 9 years ago 
I am adding header through FROM

Content-Type

application/json

Original comment by markjwil...@gmail.com on 21 Mar 2013 at 4:34

GoogleCodeExporter commented 9 years ago 
I'm having the same issue - Request Headers are not restored when selecting a 
request from History. 

When I click the request on the History page itself, the header is present - 
shown as "Content-Type: application/xml" in the 3rd column, but after I click 
Select - the value of the Headers textarea is not populated.

Original comment by usho...@gmail.com on 29 Sep 2013 at 10:36

GoogleCodeExporter commented 9 years ago 
Same issue. Content-type is never get saved. Tired of entering again and again 
:(

Original comment by hdsing...@gmail.com on 8 Oct 2013 at 6:05

GoogleCodeExporter commented 9 years ago 
Normally Content-Type header is not shown in headers panel. There is a select 
box in the form called Content Type and it should appear there.
However note that GET and HEAD requests do not carry payload so there's no need 
to set  Content-Type header.

Original comment by jarro...@gmail.com on 9 Oct 2013 at 7:37

GoogleCodeExporter commented 9 years ago 
Same issue,
I have to use the header Content-Type: application/json to a webservice with 
every GET, without it I get a UnsupportedMediaType so certainly the 
Content-Type header is passed along in a GET.

Original comment by Tim.Gei...@gmail.com on 10 Dec 2014 at 7:40