[BUG] HTTPS connection closes between messages while using HTTP Sender with SSL Enabled #6304
Labels
bug
Something isn't working
Fix-Commited
Issue fixed and will be available in milestone
Internal-Issue-Created
An issue has been created in NextGen's internal issue tracker
RS-12958
triaged
Milestone
Describe the bug
When using the HTTP Sender connector type with SSL enabled, Mirth Connect closes the TCP connection after each message, requiring the additional overhead of opening a new connection and performing the TLS handshake for each subsequent message. It seems that if the server requires a client certificate (Client Authentication = Require), then the client uses a new port for each message. If the server does NOT require a client cert (Client Authentication = Disabled), then the client uses a single connection.
To Reproduce
Setup steps (if required) and steps to reproduce the behavior:
Expected behavior
Using the HTTP Sender connector type with SSL enabled, with Client Authentication = Required, should not close the connection between each message; it should stay connected.
Actual behavior
When using the HTTP Sender connector type with SSL enabled, and Client Authentication = Required, Mirth Connect closes the TCP connection after each message, requiring the additional overhead of opening a new connection and performing the TLS handshake for each subsequent message.
Screenshots
N/A
Environment (please complete the following information):
Workaround(s)
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: