[FIXED] Invalid JS ACK for subject with '@' character #6777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Streams, consumers and subjects are allowed to have
@
characters, but JS ACKs would be invalid if a client requests messages from a consumer leader and is not directly connected to the server hosting that leader.When publishing a message with subject
[email protected]
, a client would receive the following from the server:Instead the following should be sent/received:
Clients would either recognize the invalid JS ACK and return errors, or for clients that would allow to
msg.Ack()
, the server would not be listening on that subject and the message would not be acked.Signed-off-by: Maurice van Veen [email protected]