Closed PatrickMNL closed 1 year ago
@andrii-bodnar I don't mind picking this up myself, if I can get permissions to open pull requests.
I am wondering though, whether this one should be fixed in this client package, or that it would be better to fix this on the API server side. Considering we're not sending a body (read as no content) and the server still demanding a specific content header.
I am wondering though, whether this one should be fixed in this client package, or that it would be better to fix this on the API server side. Considering we're not sending a body (read as no content) and the server still demanding a specific content header.
It looks like this is a pretty unique case since it's the only (probably) API method that doesn't require a request body schema. It would be great to fix this on the client side, and I'll also pass this on to the development team for further investigation on the server side.
Current:
The call
BundleApiExector.ExportBundle()
akaPOST api/v2/projects/{projectId}/bundles/{bundleId}/exports
doesn't require any content, the package doesn't send any as expected, however when using it, the API now returns the following;Expected: Either the API shouldn't expect the
Content-Type
field on this call, or it should be set through the package (which would require creating JsonContent even though none is included).