Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix incorrect header for message id in ACK frames #118

Merged
merged 1 commit into from
Mar 21, 2022

Conversation

Delorus
Copy link

@Delorus Delorus commented Mar 20, 2022

http://stomp.github.io/stomp-specification-1.2.html#ACK

The ACK frame MUST include an id header matching the ack header of the MESSAGE being acknowledged.

So, instead of "ack" header ACK frame must include "id" header

http://stomp.github.io/stomp-specification-1.2.html#ACK

> The ACK frame MUST include an id header matching the ack header of the MESSAGE being acknowledged.

So, instead of "ack" header ACK frame must include "id" header
@worg
Copy link
Collaborator

worg commented Mar 21, 2022

LGTM

@worg worg merged commit 7b50115 into go-stomp:master Mar 21, 2022
} else {
f.Header.Set(frame.Ack, messageId)
f.Header.Set(frame.Id, messageId)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Delorus @worg

It is my understanding that only ACK frames should use the id header. This MESSAGE frame should still use ack header. https://stomp.github.io/stomp-specification-1.2.html#MESSAGE

Or am I mistaken ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dselim you're right, sorry my bad 😔

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no worries!

@worg
Copy link
Collaborator

worg commented Mar 23, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants