on 12-22-2017 8:46 PM
Is it because of $expand being used? I see something about it in OData V2 documentation on "Representing Collections of Entries"
http://www.odata.org/documentation/odata-version-2-0/atom-format/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The response is a valid xml. No issue there. The only problem is its missing "<?xml version="1.0" encoding="utf-8"?>" . Rather it starts with <Feed tag. Its being consumed in cURL and there they have a validation to look for xml tag in OData response. That check if failing. Thats whats causing the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Only the metadata call has version and encoding details the actual data has only version details but as mentioned by Iftah how does it matter.
Also your OData call is for data and not metadata.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
And what kind of problems is it causing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Its being consumed in cURL. And there they have a validation to make sure the response has xml tag in it. That validation if failing. Even without xml tag its still a valid XML response so either they remove that check or add the missing xml tag themselves. But they have this check for other services too and above all it was working fine on OData version 1.0 so its coming back on us to makes sure response has xml tag in it.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.