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

flashproxy is effectively disabled after 5 failed connections #8

Closed
infinity0 opened this issue Mar 7, 2014 · 2 comments
Closed

flashproxy is effectively disabled after 5 failed connections #8

infinity0 opened this issue Mar 7, 2014 · 2 comments

Comments

@infinity0
Copy link

I fixed this just now upstream:

https://gitweb.torproject.org/flashproxy.git/commitdiff/05b9c101ba9afe4653d1eff6f5414f90f22ef042

I guess this is more important for cupcake, since people leave their browsers running for longer periods of time. In my experience it takes about a day to reach 5 failed connections, then after that the unfixed flashproxy is useless.

(Generally, you probably want to have some way of being notified about changes to flashproxy.js from us upstream.)

@glamrock
Copy link
Owner

@infinity0 Aha! Many thanks. Overlooked this while in the Bay.

I typically check for upstream changes about once a week.

@glamrock
Copy link
Owner

Incorporated @infinity0's upstream patch. Thanks!

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

2 participants