-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
filter.watch() does not handle sticky sessions #1665
Comments
I noticed that |
I also have this problem. I access a parity node farm behind a load-balancer that sets sticky sessions based on cookies. Some of the flows like creating and using filters require that we reach the same node. If the correct cookie value is not sent when we want to fetch events from the filter we just created this will not work. @ianthpun did you manage to get this to work? |
I merged and fixed the tests, can you test develop? |
Web3 v0.19.x didn't handle cookies correctly, which mean AWS couldn't implement load balancing with sticky sessions: web3/web3.js#1665 This updates us to 0.20.x.
Web3 v0.19.x didn't handle cookies correctly, which mean AWS couldn't implement load balancing with sticky sessions: web3/web3.js#1665 This updates us to 0.20.x.
Web3 v0.19.x didn't handle cookies correctly, which mean AWS couldn't implement load balancing with sticky sessions: web3/web3.js#1665 This updates us to the current development tip.
Currently, filter.watch() doesn't seem to support sticky sessions. The initial call to
web3.eth.filter('latest')
does not hold the cookies set from the responseThe text was updated successfully, but these errors were encountered: