Server rejectes as Unsupported media type because Content-Type is missing for POST about angular-swagger-ui

[mathieuales]

Hi !

Thanks for using angular-swagger-ui.
It's a documentation issue :-( when using 0.1.6 you should use directive as described below to enable request transformation:

<div swagger-ui
     url="swaggerUrl"
     api-explorer="true"
     error-handler="myErrorHandler"
     api-explorer-transform="myTransform">
</div>

Then make sure your swagger API descriptor defines the Content-Type of your operation in its definition see consumes parameter

You can also take a look at the example in dist/index.html.

Hope this helps !

[konczak]

I think that integration of Angular-Swagger-Bootstrap is awesome idea - thank you for your work!

You are right that I should use api-explorer-transform in 0.1.6 so I change it but issue still remain the same.

I know that Content-Type served by server has to be in place and it is as you can see:

 "post":{
    "tags":[
       "place-api"
    ],
    "summary":"Add new Place [HR]",
    "description":"Returns created Place",
    "operationId":"addUsingPOST",
    "consumes":[
       "application/json"
    ],
    "produces":[
       "*/*"
    ],
    "parameters":[
       {
          "in":"body",
          "name":"placeNew",
          "description":"placeNew",
          "required":true,
          "schema":{
             "$ref":"#/definitions/PlaceNew"
          }
       }
    ],
    "responses":{
       "200":{
          "description":"Create new Place",
          "schema":{
             "$ref":"#/definitions/Place"
          }
       },
       "201":{
          "description":"Created"
       },
       "400":{
          "description":"Invalid input"
       },
       "401":{
          "description":"Unauthorized"
       },
       "403":{
          "description":"Forbidden"
       },
       "404":{
          "description":"Not Found"
       }
    }
 }

And you can see application/json content in the UI to choose and that body is specified as well:

[mathieuales]

I found the issue, it ill be fixed in next release ASAP.
Workaround: all parameters in body must be named "body" in your Swagger API descriptor.

[mathieuales]

should be fixed in 0.2
can you confirm ?