[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #11400 [Flashproxy]: Status lists itself as "dead" inaccurately



#11400: Status lists itself as "dead" inaccurately
----------------------------+--------------------
     Reporter:  saint       |      Owner:  dcf
         Type:  defect      |     Status:  closed
     Priority:  normal      |  Milestone:
    Component:  Flashproxy  |    Version:
   Resolution:  fixed       |   Keywords:
Actual Points:              |  Parent ID:
       Points:              |
----------------------------+--------------------

Comment (by dcf):

 Replying to [comment:3 saint]:
 > Replying to [comment:2 dcf]:
 > > Here's a summary of my thinking:
 > >  1. The code transitions to "dead" in all the places it was meant to.
 > >  2. However, "dead" doesn't work the way it was meant to: it was
 supposed to turn off all future network activity, just like "disabled"
 does.
 > >  3. However however, it appears that this behavior is not what Cupcake
 wants--it wants to continue polling after a network error.
 > >
 > > How do these patches work for you? An alternative to the second patch
 is to increment a counter or something, and then actually die (up until
 the next daily refresh) after a threshold is passed.
 >
 > I agree with your line of thinking - dying works well on a standard page
 because refreshing the page automatically restarts flashproxy.js.  In
 Cupcake's Chrome extension, things get trickier because it's running in
 the background until browser restart (Linux) or *system* restart
 (Win/OSX).  Patch 2 has tested as fine, so is being merged.  This 'bug'
 usually appears when someone is behind a captive portal, so it letting it
 attempt to poll the facilitator again seems like it would be fine.  And as
 you point out, this is Cupcake's default behavior currently, just with an
 error status.
 >
 > I may add a counter in addition to Patch 2 just to keep the original
 failsafe behavior intact.  Thank you for the patch =)

 Actually I meant to apply these patches to the main flashproxy.git. Does
 that work for you?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11400#comment:5>
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