Request Headers could be displayed when you "Try it out!"

[ecourreges-orange]

When you click "Try it out!",
Everything from the request/response is there and displayed nicely in the UI except for the Request Headers which are necessary for some APIs.
As such you are forced to use firebug or wireshark on the side to get them.

[fehguy]

The request headers are easily available in swagger ui. Would be helpful if you put a screenshot or mock of what you're suggesting.

[ecourreges-orange]

When you click try it out, you get:

Request URL

http://host:80/url?querystring

Response Body

{
  "error": {
    "code": 13,
    "message": "Invalid Credential Value",
    "description": "A credential value given by the client does not conform to the validation function of this credential type"
  }
}

Response Code

400

Response Headers

{
  "Date": "Tue, 28 Oct 2014 18:31:00 GMT",
  "Server": "Apache",
  "X-Pns-Request-Id": "PNSWS31-27410428",
  "Content-Length": "203",
  "Content-Type": "application/json; charset=\"utf-8\"",
  "Connection": "keep-alive"
}

So the only obviously missing section is "Request Headers", which could be placed right after Request URL and look like this:

Request Headers
{
  "User-Agent": "Your Browser",
  "X-USER-ID": "PNSWS31-27410428",
  "X-Another-Header": "another value",
  "Accept": "application/json; charset=\"utf-8\"",
  "Connection": "keep-alive"
}

There could also be an option in your swagger json description to decide if you want request headers to appear or not, which is something that I haven't found.

[webron]

I think this is similar to #273.

[fehguy]

This should be a configuration. I don't think you always want request headers to be shown, as they can have api keys, passwords, etc.

[webron]

Fix is merged in develop_2.0.