-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExtensionsV1beta1Api.patchNamespacedDeployment throws 500 Internal server error because of wrong content type in header #127
Comments
Same error when calling |
Any word on this issue? |
@mjschmidt |
How can we use a JsonPatch to patch a Node? |
reason: content-type in header is being set to application/json-patch+json instead of application/strategic-merge-patch+json
this is causing 500 internal server error
when i test the patch call to /apis/extensions/v1beta1/namespaces/default/deployments/kubeexample?pretty=false with content type as application/json-patch+json (in postman rest client) , getting following error
I believe content type should be application/strategic-merge-patch+json (with it as content type deployment gets updated)
in ExtensionsV1beta1Api.patchNamespacedDeploymentCall
localVarContentTypes is being set to application/json-patch+json instead of application/strategic-merge-patch+json because of ApiClient.selectHeaderContentType(String [] arr) always select first element of array({"application/json-patch+json", "application/merge-patch+json", "application/strategic-merge-patch+json"}) as it matches with regex.
The text was updated successfully, but these errors were encountered: