Read more for Design Specification
Many may wonder why we don't use tools like Nginx, Traefik, or Kong, which already serve as gateways. From my observations, these options do not necessarily provide a configuration simplicity that end-users can easily manage. Additionally, it appears that, for the most part, these tools are designed for static values that can be transformed in the response, without the ability to incorporate additional conditions, such as based on the path or specific requests.
If anyone is familiar with a project that addresses similar concerns, I would appreciate some recommendations. Thank you.
- nginx: https://nginx.org/en/docs/http/ngx_http_proxy_module.html...
- traefik: https://plugins.traefik.io/.../628c9f.../replace-status-code https://github.com/traefik/plugin-rewritebody https://github.com/traefik/traefik/issues/2039
- Kong: https://docs.konghq.com/hub/kong-inc/response-transformer/
- YARP https://github.com/microsoft/reverse-proxy/blob/release/1.1/docs/docfx/articles/transforms.md
- lua-nginx-module: https://gist.github.com/ejlp12/b3949bb40e748ae8367e17c193fa9602
- Tyk: https://tyk.io/docs/advanced-configuration/transform-traffic/response-body/#response-body-transformation
Some tools can also be proxy or gateway:
- wiremock: https://wiremock.org/
- mountebank: https://www.mbtest.org/
Modify HTTP Response Reverse Proxy
build for M1
docker buildx build --platform linux/amd64 -t spy .
docker run --rm -p 3333:3333 spy