Artem Martynenko

Hi. This solution directly implement workflow described on stackoverflow. If you have separate web client, on first request to the resource server client will get response with 302 status code...

downstream services are load balanced by default in spring cloud gateway. You just need to set route url like "lb://service-name"

It looks like the blocker issue with body modification is already [solved](https://github.com/cloudflare/pingora/commit/cc32316980371ea5aacf7339d7421f3041c4c505) Do you have any plans to implement proxy-wasm in the near time?