It does, but it looks like it’s not working as it should, there is a FormData
parameter that should handle URL encoding values in a GET
If you take a look at the other post regarding matching in query strings, the workaround is to use a middleware/redirect/virtual path combo.
Looks like you lost a paragraph there, I assume that you mean you want the middleware - which is functionally meant to modify and transform data as it passes through the gateway - as a way to hijack and return different data to the user. This has been requested many times and is something we are looking at.
We’d suggest putting this code into the tyk.js
file, it gets loaded into all JSVM sandboxes, so you can access the functionality there.
That looks lovely - feel free to add a feature request Though we’re not going to be completely overhaul how the Endpoint designer and associated functionality works any time soon.