Data API set container failing

OttoFMS
1

Hi. I have a setContainer() call that I’ve been using in Swift for a long time now, prior to Otto. If I append /otto to the path and pass the Otto proxy token, I’m getting an error in the console (Xcode):

Message(code: “1708”, message: “Invalid content type (application/json). These are valid: multipart/form-data”)

My call uses multipart/form-data. If I remove /otto from the path and go back to a standard, non-proxy Data API token, the setContainer() call works fine.

Any thoughts as to why? If I do change multipart/form-data to something else say, image/jpeg, the error still says invalid content type application/json. It’s like it’s ignoring whatever was passed as the Content-Type.

This is only affecting setContainer(). All of my non-container calls work fine with Otto (4.6.2).

2

Hey @bhamm ,

Looks like this is an error on our side. We’re not passing the content-0type all the way through. I’ll get that fixed in our next version. Thanks for the report!

-Kyle

1 Like
3

Hey @bhamm ,

This issue is fixed with OttoFMS version 4.7.1! Let me know if you have any issues with it going forward.

-Kyle

1 Like
4

Hooray! :tada:

Thanks for following up. I’ve sent an email to support to get my (hosted) server upgraded.

1 Like