fix(catalog/rest): Do not set Content-type header in doPost #268
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change shouldn't really be necessary..... but I just spent the better part of an afternoon tracking it down.
I've been testing against snowflake opencatalog and it appears that they're running some older version of
polariswhere a bug exists where if you specify aContent-Typeheader multiple times on aPOSTyou'll get a cryptic 400 back from the server. I wasn't able to find a bug inapache/polaris, but the problem doesn't happen on main.Seems safe to do as the header is defaulted here.