ContributionsMost RecentMost LikesSolutionsRe: OpenAPI not encoding multipart/mixed correctly Yes we have the same problem with multipart/mixed and multipart/form-data not being rendered correctly when it generates the cURL command. We have a bug-fix request with Smartbear for over one month now and still no resolution. And apparently the issue has been there for quite some time. According to their documentation it should work. This is really becoming a big issue for us now. Not sure why taking them so long to fix this problem. Re: OpenAPI v3.0.1 support in SoapUI open source? We are having same issue. Can anyone help with this ? Re: Accept header generated in lower case not working in "Try It Out" or with cURL Apologies everyone, it seems that the issue is with the API that we're calling. Apparently it does the header validation in code and it only checks for "Accept" not "accept". Unfortunately cannot change the code and still not sure how to pass the upprcase "Accept" through "Try It Out" but at least the mystery is solved. Re: Accept header generated in lower case not working in "Try It Out" or with cURL Yes, absolutely. My oversight, I had changed the text to a bogus host but not the link underneath. Thanks Accept header generated in lower case not working in "Try It Out" or with cURL The "Try It Out" and cURL generated gives error on Accept Header. Seems the accept header is being generated with lower case. With cURL when we change "accept" to "Accept" we get a proper response. How can we make the header being generated as upper case initial letter ? curl -X 'GET' 'https://host.com/cm/accounts/19415703 ' -H 'accept: application/json' -H 'x-api-key: xxxxxx' -H 'Authorization: Bearer xxxx' We’re getting this error when trying out one of the methods in our sample API: { "code": null, "description": "Expected Accept in headers", "status": 400 } We cannot release the documentation to consumers with this problem. Thanks in advance for your prompt response with a resolution to this.