When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID backto the caller in the HTTP response header.
How can this be achieved?
A.
Enable the auto-generate CorrelationID option when scaffolding the flow
B.
Enable the CorrelationID checkbox in the HTTP Listener configuration
C.
Configure a custom correlation policy
D.
NO action is needed as the correlation ID is returned to the caller in the response header by default
When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID, which is returned to the caller in the response header by default as MULE_CORRELATION_ID. References: https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#mess age-attributes
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit