Fix multi-part form Content-Disposition Headers #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…i-part form data against certain APIs
|
@Zaid-Ajaj - any luck? Would love to get this merged as it's blocking for us. |
Zaid-Ajaj
added a commit
that referenced
this pull request
Apr 8, 2024
|
Hi @varon this is merged and published as of Hawaii v0.69 🚀 it should be available on nuget soon |
|
Thank you! absolutely appreciated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With the default generation of these headers, Stability API's platform was not correctly handling the content-disposition headers and was rejecting our requests with
BAD REQUEST.This patches the behavior to explicitly set these headers - which solves the issue.
This isn't the most elegant solution, but it does address the problem - I'm open to more elegant approaches if you can suggest them.