HTTP Reply Nodes fail to recognise duplicate replies (SOAP Reply nodes do detect this)

When a HTTP timeout occurs using a broker-wide listener, the
processing thread continues to process resulting in an attempt to
submit a duplicate HTTP response message.

When using SOAP Nodes, this duplicate response attempt results in an
exception (as expected) - you cannot reply more than once using the
same reply identifier:

BIP3743 : An attempt was made to use a message
after it had timed out. The message was
.

However, when using HTTP nodes, the HTTP reply node fails to validate
whether the reply identifier has been consumed, you can actually place
a series of HTTP Reply nodes in a row and no exception occurs.

In this respect (unable to submit duplicate replies), HTTP Services and
SOAP Services (over HTTP) should behave in a consistent manner -
duplicate replies should not be possible, and the BIP codes returned -
in theory, could be identical when such an error occurs.

...or at least, HTTP nodes should return a BIP code that this specific to this error, much like the SOAP nodes do (when used over HTTP).