Artem Bilan

Are you sure that there is no way to make that sample project much simpler? It is really hard to understand what is going on with so much custom code....

Yeah... Would be great to be able to reproduce with a simple project and even without Azure and Spring Cloud at all. Right now there are too much stuff to...

It look like this one is an answer for a first request: ``` 2022-10-14 09:20:08.278 DEBUG 1 --- [or-http-epoll-4] c.b.p.config.client.WebClientConfig : Response status: 204 NO_CONTENT ``` so, no content -...

``` .route(Message.class, "SOME CHANNEL name") ``` ??? This one calls the API like: ``` /** * Populate the {@link MethodInvokingRouter} for the method * of the provided service and its...

I also see in your logs something like this: ``` 2022-10-14 09:20:38.248 DEBUG 1 --- [oundedElastic-5] o.s.integration.handler.LoggingHandler : Outbound gateway payload : ``` Which is apparently a response for that...

So, your logic looks like this: 1. Send a request. 2. If `204` response send a create request via the same HTTP gateway. 3. Then you go to some `REVERT_TO_ORIGINAL_PAYLOAD_CHANNEL`...

Yeah... I see your point. So, in logs there is present this line: ``` 2022-10-14 09:20:08.343 DEBUG 1 --- [or-http-epoll-4] o.s.i.h.support.DefaultHttpHeaderMapper : setting headerName=[cache-control], value=private ``` Which is the last...

Glad to hear that we have localized a culprit! 😄 Can you, please, confirm what is the workaround? Can we reproduce the problem without Spring Integration?

Hi there! Any news? Do we still have a problem from Spring Integration perspective? Or we simply can close with a `Works as Designed` label?

Sorry, until AWS Labs fixes issues mentioned in that SI-AWS issue I've just commented your back, we cannot move on.