search

timothyjohncarney / chrome-rest-client

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

Custom "Accept" header for GET and HEAD methods #204

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a GET request to https://jira.atlassian.com/rest/auth/1/session
2. Run the request with the default Content-Type: text/html;charset=utf-8

What is the expected output?
Expected status code 200

What do you see instead?
Received status code 406
415 Unsupported Media Type

On what operating system, browser and browser version?
Gentoo Linux 3.4.4
Chromium 23.0

Please provide any additional information below.
I have tested with REST Console.
https://chrome.google.com/webstore/detail/rest-console/cokgbflfommojglbmbpenpphp
pikmonn/related

There I have tried different "Accept" headers.
Accept: application/json - received code 200
Accept: text/html - received code 406

Please introduce custom "Accept" header

Original issue reported on code.google.com by KoichiSe...@gmail.com on 5 Sep 2013 at 9:15

GoogleCodeExporter commented 9 years ago 
You can install REST Console and try it for different "Accept" request headers: 
https://chrome.google.com/webstore/detail/rest-console/cokgbflfommojglbmbpenpphp
pikmonn

Original comment by KoichiSe...@gmail.com on 5 Sep 2013 at 9:16

GoogleCodeExporter commented 9 years ago 
It appears like I have missed the "Headers" section of the application.
While the POST, PUT, PATCH, DELETE, OPTIONS methods have the custom 
"Content-Type" drop-down menu field which I used to specify "application/json" 
type, it is not available for the GET and HEAD methods, that's what I have 
meant.
But there is the actual "Headers" section where one can type the "Accept" and 
"Content-Type" headers manually.
I was just confused with the GUI, so this issue is rather about the layout.

Original comment by KoichiSe...@gmail.com on 5 Sep 2013 at 12:00

GoogleCodeExporter commented 9 years ago 
In new version that I'm working on right now, there will be no content-type 
section below payload form. I agree that it may confusing some people and it is 
not so important.

Original comment by jarro...@gmail.com on 6 Sep 2013 at 5:01