[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #11400 [Flashproxy]: Status lists itself as "dead" inaccurately
#11400: Status lists itself as "dead" inaccurately
------------------------+---------------------
Reporter: saint | Owner: dcf
Type: defect | Status: new
Priority: normal | Milestone:
Component: Flashproxy | Version:
Keywords: | Actual Points:
Parent ID: | Points:
------------------------+---------------------
So right now, rapid network changes will trigger a false [dead] signal and
seemingly remain that way. However, it is not actually dead or disabled in
any way, just idle. It will still become [active], and afterwards it
returns to a typical [idle] state.
This happens in a no-internet environment and when behind a captive
portal. (Which, given that I am frequently behind captive portals, this
likely happens more than with most users).
'''Proposed fixes''':
* Change [dead] to [waiting], since it seems to be waiting for a real
connection
* Ensure that flash proxies with dead/waiting status occasionally re-
check connection
(this isÂ[https://github.com/glamrock/cupcake/issues/9 Cupcake issue #9])
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11400>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs