Airidas36

> What you have described is the expected behavior. If the response has been committed already, headers and partial body might have been sent to the client over the network...

> We did switch from collecting into a List to streaming. This reduces memory usage but also provides control to collect via `Fux#collectToList()` if needed while with collecting by default...

> Hi, I will look into that. In the meantime, can you please explain what's the use-case for reactive scheduled method. Thanks Hi, Previously, if code-base was reactive, it was...

@jamesforwardnwboxed We are experiencing the same issue when application is sitting behind a load balancer. This issue was discovered only after the deployment since unit/integration tests / running it on...

While `server.forward-headers-strategy=none` worked for us in most cases, it still breaks things when we have a gateway running as a proxy between frontend and backend with Spring Security and CORS,...

> [@Airidas36](https://github.com/Airidas36) what do you think gateway should do here? I do agree with @capnrotbart that this behavior should definitely be documented. I would expect that by default no rewrite/re-route...