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

Surface proxy errors #37

Closed
willscott opened this issue Apr 17, 2014 · 3 comments
Closed

Surface proxy errors #37

willscott opened this issue Apr 17, 2014 · 3 comments
Labels

Comments

@willscott
Copy link
Member

Issue by willscott from Fri Oct 18 19:25:17 2013
Originally opened as https://github.com/UWNetworksLab/UProxy/issues/103


chrome surfaces errors with requests to the set up proxy off of something like chrome.proxy.onError.addEventListener. If the proxy is a uproxy-configured proxy, we should be listening for such errors to see if something is up / change the icon / suggest other peers / stopping / etc.

@willscott willscott added this to the v0.8 Allardice Feature Complete milestone Apr 17, 2014
@scouttle
Copy link

It sounds like this is Chrome-specific; is there a parallel in Firefox that should be plumbed up as well?

@willscott
Copy link
Member Author

Presumably yes.
It won't be part of the same interface though, and will instead have to do with looking at general request timeouts / error, probably.

For future reference, firefox proxy interface example usage is here:
https://stackoverflow.com/questions/10605183/how-to-change-firefox-proxy-settings-using-xpcom

@dborkan
Copy link
Contributor

dborkan commented Oct 13, 2014

Done, although there are some issues with this currently being looked at in https://github.com/uProxy/uproxy/issues?q=is%3Aopen+author%3Alucyhe

@dborkan dborkan closed this as completed Oct 13, 2014
trevj added a commit that referenced this issue Dec 7, 2016
pull banner from the current installation, if available
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants