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…

[image] Schwartz_David: I'm using the TRESTClient/Request/Response components, and this is all I can get. It looks like a problem with your TRestClient configuration. It seems it's sending the content type as application/x-www-form-urlencoded.

Yes, I know. The question is WHY? I have it set for application/json wherever I can set ContentType in the Object Inspector and I cannot override it in code since the property cannot be assigned to. It's being over-written somehow. I've found lots of people complaining about this and there was a pro…

I don't know, I"m not very familiar with TRESTClient as I mostly use our own THttpClient from Sparkle. But well, try to change all properties from code and post it here so we at least can have an idea of what you're doing without guessing.

Ok, I hooked up Sparkle's THttpClient and fed it this: Request := Client.CreateRequest; Request.Uri := 'http://localhost/MyService/DoThis'; Request.Method := 'POST'; Request.Headers.SetValue('aFocus1', 'aaaaa'); Request.Headers.SetValue('aFocus2', 'bbbbb'); Request.Headers.…

UPDATE: I can run this as a GET operation and it works. So there's something weird about how the parameters are being sent. Also, I tried adding these, but they didn't make any difference. Request.Headers.SetValue('accept', 'application/json'); Request.Headers.SetValue('Content-Type', 'applica…

[image] Schwartz_David: That seems a little more informative than the previous error, but I still don't know what to make of it. Well, you are sending an invalid JSON, and that's what the message says to you: you have an invalid character at the beginning of the text. Send a valid JSON instea…

But I'm not sending any JSON. I'm just posting name-value pairs into the header via Request.Header.SetValue(...). I'm assuming it's turning them into JSON itself as part of the POST request. Or am I not constructing the Request properly? (It would be nice to see some examples in the doc there; it's…

[image] Schwartz_David: Request.SetContent(TEncoding.UTF8.GetBytes('Request content')); You are sending this. Why are you doing that? How is your service implemented? What DoThis expects?

I don't really know what this stuff is for. Please show me some examples of POST and GET requests using Sparkle's THttpClient that I can follow. There are just fragments in the Sparkle docs and the same material is in the XData docs. I find this whole topic quite annoying because there are nearly a…

I forgot to mention that my code was adapted from the Sparkle example given where a POST request was used instead of a GET request that would have sufficed. That's not a big deal, but it did not include sending any parameters to the host, and it DID include the line you asked me why I used it. The a…

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

BIZ TMS XData

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

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

Related topics