{"action":"created","issue":{"url":"https://api.github.com/repos/spion/sticky-listen/issues/1","labels_url":"https://api.github.com/repos/spion/sticky-listen/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/spion/sticky-listen/issues/1/comments","events_url":"https://api.github.com/repos/spion/sticky-listen/issues/1/events","html_url":"https://github.com/spion/sticky-listen/issues/1","id":113738728,"number":1,"title":"Use headers instead of socket IP","user":{"login":"spion","id":502412,"avatar_url":"https://avatars.githubusercontent.com/u/502412?v=3","gravatar_id":"","url":"https://api.github.com/users/spion","html_url":"https://github.com/spion","followers_url":"https://api.github.com/users/spion/followers","following_url":"https://api.github.com/users/spion/following{/other_user}","gists_url":"https://api.github.com/users/spion/gists{/gist_id}","starred_url":"https://api.github.com/users/spion/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spion/subscriptions","organizations_url":"https://api.github.com/users/spion/orgs","repos_url":"https://api.github.com/users/spion/repos","events_url":"https://api.github.com/users/spion/events{/privacy}","received_events_url":"https://api.github.com/users/spion/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-10-28T03:55:07Z","updated_at":"2015-10-28T19:17:49Z","closed_at":null,"body":"Parse the HTTP headers and use the cookie or the IP in the `x-forwarded-for` header - this should work better when there are additional load balancers between the cluster and the client.\r\n\r\nWhat should the strategy be though? Cookie, fallback to x-forwarded-for, fallback to ip address? How to gracefully handle no-cookie -> cookie transition?"},"comment":{"url":"https://api.github.com/repos/spion/sticky-listen/issues/comments/151961975","html_url":"https://github.com/spion/sticky-listen/issues/1#issuecomment-151961975","issue_url":"https://api.github.com/repos/spion/sticky-listen/issues/1","id":151961975,"user":{"login":"spion","id":502412,"avatar_url":"https://avatars.githubusercontent.com/u/502412?v=3","gravatar_id":"","url":"https://api.github.com/users/spion","html_url":"https://github.com/spion","followers_url":"https://api.github.com/users/spion/followers","following_url":"https://api.github.com/users/spion/following{/other_user}","gists_url":"https://api.github.com/users/spion/gists{/gist_id}","starred_url":"https://api.github.com/users/spion/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spion/subscriptions","organizations_url":"https://api.github.com/users/spion/orgs","repos_url":"https://api.github.com/users/spion/repos","events_url":"https://api.github.com/users/spion/events{/privacy}","received_events_url":"https://api.github.com/users/spion/received_events","type":"User","site_admin":false},"created_at":"2015-10-28T19:17:49Z","updated_at":"2015-10-28T19:17:49Z","body":"@Ajaxy To add a cookie, sticky-listen will also have to intercept the server response and add the cookie there, not just the request. Since the socket has been handed off to the other worker already, I doubt that I can make that work at all.\r\n\r\nI think its best to go with a simpler solution that uses the IP address in `x-forwarded-for` first... then if thats not enough we'll try to improve it."}}