[Http Retry] Response headers interference

[joepkalthoff]

Summary

Retries in the Http component include headers from the previous (re)try.

Testcase

Dovetail version: 4.17.0-SNAPSHOT-dcb7cc8 Instance: next Tenant: Regression Tests

Sending Flow: HttpRetrySocketAsynchronous Flow version: 7 url: https://next.dovetail.world/flowdesigner/66b1efbde56ba4001000012e/7/route

Receiving Flow: HttpRetry500 Flow version: 1 url: https://next.dovetail.world/flowdesigner/66b31c0ee56ba4000e00002f/1/route

Input:

• Make sure the flow is installed in test and kick off the flow: https://next.dovetail.world/test/inbound_http/regressiontests/HttpRetrySocketAsynchronous

Output: Notice the transactions of the Sending flow and the Receiving flow. Especially the body and headers for the first try and the 2 retries. There are screenshots in the results section below:

Result

Initial Http request

Sending

Receiving

1st retry

Sending

Receiving

2nd retry

Sending

Receiving

After the Http retries

Conclusion

I expect the headers from the 5xx responses to not interfere with the retry messages. Only the breadcrumbId, Content-Type and counter header should be included.

There should be a way to see the response headers somewhere though. They can contain valuable information about why the server responded with a 5xx in the first place. Maybe in the Logs of a flow?

The same is true for the 5xx response body. This is a seperate issue: https://github.com/assimbly/runtime/issues/268.

Original issue on Dovetail Application board: https://github.com/dovetailworld/front-end/issues/4635.