You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to use POST request (with X-HTTP-METHOD = GET header) instead of GET, since in some cases the query is too long and you may face to error 414 URI Too Long.
I have used the DF API for this (verb tunneling via POST), but it is odd that it behaves differently and not working properly:
if I send the payload as { ids: "228, 229", id_field: "id" }
it won't work, but I realized that if I use the payload as in the following, it works fine! { filter: "id IN (228, 229)" }
it seems a bit weird to me and if this tunneling feature is fully compatible with all queries.
thanks for your attention
The text was updated successfully, but these errors were encountered:
I need to use POST request (with X-HTTP-METHOD = GET header) instead of GET, since in some cases the query is too long and you may face to error 414 URI Too Long.
I have used the DF API for this (verb tunneling via POST), but it is odd that it behaves differently and not working properly:
if I send the payload as
{ ids: "228, 229", id_field: "id" }
it won't work, but I realized that if I use the payload as in the following, it works fine!
{ filter: "id IN (228, 229)" }
it seems a bit weird to me and if this tunneling feature is fully compatible with all queries.
thanks for your attention
The text was updated successfully, but these errors were encountered: