You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm facing an issue where multiple streams with different grip-channel will receive data of other grip channel. It won't happen on the initial connection, instead it happens when pushpin calls the url in grip-link returned by the initial connection, and when both stream are established in nearly same time.
My header is like this "Grip-Channel": "1076063" "Grip-Link": "</stream/subscribe/transaction?id=01EH2>; rel=next"
I've tried on pushpin, as well as fanout hacker plan. Both are able to simulate this issue.
Any idea why? Thanks.
The text was updated successfully, but these errors were encountered:
Pushpin does "request collapsing" if it would need to request the same link on behalf of multiple connections. Also, any GRIP instructions in the response to that request will be applied to the connections. Could it be that you're responding with the wrong Grip-Channel header(s) in the link response, causing the subscribed channels to change?
Hi, I'm facing an issue where multiple streams with different grip-channel will receive data of other grip channel. It won't happen on the initial connection, instead it happens when pushpin calls the url in grip-link returned by the initial connection, and when both stream are established in nearly same time.
My header is like this
"Grip-Channel": "1076063"
"Grip-Link": "</stream/subscribe/transaction?id=01EH2>; rel=next"
I've tried on pushpin, as well as fanout hacker plan. Both are able to simulate this issue.
Any idea why? Thanks.
The text was updated successfully, but these errors were encountered: