Skip to content
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.

retry/invalidate when DynECT complains about changed IP #1492

Open
codefromthecrypt opened this issue Apr 3, 2013 · 0 comments
Open

retry/invalidate when DynECT complains about changed IP #1492

codefromthecrypt opened this issue Apr 3, 2013 · 0 comments

Comments

@codefromthecrypt
Copy link
Contributor

DynECT unfortunately strictly enforces reverse IP lookup within a session, which can cause temporal failures noted below

Netflix/denominator#106
codefromthecrypt pushed a commit that referenced this issue Apr 21, 2013
fix issue #1492: invalidate dynect session on ip mismatch
6fd7798
@codefromthecrypt codefromthecrypt mentioned this issue Apr 21, 2013
Merged
codefromthecrypt pushed a commit that referenced this issue Apr 21, 2013
fix issue #1492: invalidate dynect session on ip mismatch
935513e
codefromthecrypt pushed a commit that referenced this issue Apr 22, 2013
fix issue #1492: invalidate dynect session on ip mismatch
6eaf083
codefromthecrypt pushed a commit that referenced this issue Apr 22, 2013
Merge pull request #1554 from jclouds/issue-1492
630d4cf 
fix issue #1492: invalidate dynect session on ip mismatch
codefromthecrypt pushed a commit that referenced this issue Apr 22, 2013
fix issue #1492: invalidate dynect session on ip mismatch
874d835
@codefromthecrypt codefromthecrypt mentioned this issue Apr 22, 2013
Merged
codefromthecrypt pushed a commit that referenced this issue Apr 22, 2013
Merge pull request #1555 from jclouds/issue-1492-1.6.x
f03ab58 
fix issue #1492: invalidate dynect session on ip mismatch (1.6.x)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@codefromthecrypt