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

Queue processor may use x-server-timestamp set by another gateleen instance #45

Closed
lbovet opened this issue Jun 21, 2016 · 0 comments
Closed
Assignees

Comments

@lbovet
Copy link
Member

lbovet commented Jun 21, 2016

When a gateleen instance forwards to another one, the original x-server-timestamp header is used to calculate the expiration time in QueueProcessor. In case of delay or unsynchronized clocks, the expected TTL is not respected.

Proposal: add another header that would only be used internally by the queue handler. It will be set at enqueue time and removed when the request is played: x-queue-timestamp
This header would never be forwarded.
So we decouple the x-server-timestamp header and queue behaviour.

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

No branches or pull requests

1 participant