Request from .net library using custom domain results in Bad Request (400, Content type 'application/x-amf' is not allowed for upload files)

Hi support,

We’re trying to use custom domain in our application (instead of api.backendless.com).

  • Custom domain in added successfully in Backendless console. SSL is enabled.
  • Requests using api.backendless.com works fine.
  • When we replace the above mentioned url with the custom one, we get: Bad Request (400, Content type ‘application/x-amf’ is not allowed for upload files. Use ‘multipart/form-data’ or ‘application/json’.“,”)
  • The request we’re attempting to invoke is method (custom services).
  • Please check screenshot of Fiddler trace for both the cases (in screenshots the request section is followed by the response section).

Works with default url

Doesn’t work with custom url

Please suggest.

Please let me know in case any additional information would be helpful.

Hello Kinjal Desai (@Kinjal_Desai),

Thank you for bringing this issue to our attention. To resolve it, we recommend not using the custom domain within the SDK. The SDK is designed to work with the default Backendless domain, and using a custom domain can lead to unexpected errors, like the one you’re encountering.

Regards,
Alexander

Hi @Alexander_Pavelko

Thanks for your response. Its bit disappointing to know its not supported.

Your answer is quite clear but I thought to double check as, while trying to make it work, i came across this support article that talks about using custom domain in the .net sdk.

https://backendless.com/docs/dotnet/setup.html

Please suggest.

Best regards,
Kinjal

Hello @Kinjal_Desai,

Thank you for bringing this to our attention, and we apologize for the inconvenience caused. I’ve created an internal ticket to investigate this issue further. Our team is looking into it, and we will keep you updated in this thread as soon as we have more information.

Thank you for your patience!

Regards,
Alexander

Thank you, we look forward to a resolution!