There has been an increasing amount of worry with how definition expressions from the client side are publicly exposed.
Does anyone know of a way to effectively proxy the /query route to some internal service that can add the filter data (i.e. not on the client-side)? I see there is a deprecated proxy concept out there, but wanted to know if this is technically achievable through some kind of reverse proxy or perhaps there is something in-the-works that we could utilize on a future date.
