You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have noticed an issue in generated Postman collections if there is a 2xx response without content type defined. It seems very similar to issue reported in apideck-libraries/portman#392.
Here is an example of a specification, where one of responses has no content (204):
@thim81 It seems to be correct behavior to me. So Accept request HTTP header indicates which content types, expressed as MIME types, the client is able to understand.
Here, as only content-type defined in response is application/problem+json, we add accept header with that as value but in the second example/case we also have application/json so we use that.
Could you also mention what would be expected behavior according to you?
@thim81 Hi, is there any update on this? i have a delete request which does not have any content type for 204, same request has different response codes having different content type. now when i run for 204, it adds request header "Accept":"application/problem+json", which fails my test with unsupported media type. Please help me with this,
We have noticed an issue in generated Postman collections if there is a 2xx response without content type defined. It seems very similar to issue reported in apideck-libraries/portman#392.
Here is an example of a specification, where one of responses has no content (204):
Generated Postman collection will contain:
Note an "Accept: application/problem+json" in request part of a generated file.
Though if we add at least one responce with "application/json" content (201), then generated Postman collection contains "Accept: application/json".
Generated Postman collection will contain:
The text was updated successfully, but these errors were encountered: