The Swagger UI works, but I built a little test app and used the REST Debugger to connect to my service, and I keep getting this error. I set the Content Type to application/json, but the error says it's really a url-encoded form. I'm using the TRESTClient/Request/Response components, and this is …

TL;DR All of the issues I was having with my client-side apps interacting with my XData service could have been avoided if I simply stuck to using the TXDataClient instead of every other HTTP Client component I could find. Holger did use it, but somehow I got misdirected and went off into the weeds…

calling my XData server --> Unsupported media type: application/x-www-form-urlencoded

BIZ TMS XData

wlandgraf (Wagner Landgraf) Split this topic January 13, 2023, 10:13pm 4

A post was merged into an existing topic: short-term persistence across several service calls

Topic		Replies	Views
async problem TMS WEB Core	7	394	February 16, 2023
short-term persistence across several service calls TMS XData	13	442	January 13, 2023
Overriding standard REST procedures TMS XData	4	1024	September 8, 2015
XData with Sphinx authorization TMS XData	18	160	July 1, 2025
Using more complex objects with XData TMS XData	13	455	July 6, 2023

calling my XData server --> Unsupported media type: application/x-www-form-urlencoded

Related topics