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.
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.