GNOME Bugzilla – Bug 575950
Support for proxys/tor, crash when attempting to access blocked resource
Last modified: 2018-07-11 22:57:24 UTC
Currently, if you attempt to access a blocked resource (e.g. RTM), the program will simply crash: Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. RtmNet.RtmWebException: HTTP Error 403, Forbidden ---> System.Net.WebException: The remote server returned an error: (403) Forbidden. at System.Net.HttpWebRequest.CheckFinalStatus (System.Net.WebAsyncResult result) [0x00000] at System.Net.HttpWebRequest.SetResponseData (System.Net.WebConnectionData data) [0x00000] --- End of inner exception stack trace --- at RtmNet.Rtm.DoGetResponse (System.String url, System.String variables) [0x00000] at RtmNet.Rtm.GetResponse (System.Collections.Hashtable parameters) [0x00000] at RtmNet.Rtm.AuthGetFrob () [0x00000] at Tasque.Backends.RtmBackend.RtmBackend.GetAuthUrl () [0x00000] at Tasque.Backends.RtmBackend.RtmPreferencesWidget.OnAuthButtonClicked (System.Object sender, System.EventArgs args) [0x00000] at GLib.Signal.voidObjectCallback (IntPtr handle, IntPtr data) [0x00000] at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal) at GLib.Signal.voidObjectCallback(IntPtr handle, IntPtr data) at GLib.Signal.voidObjectCallback(IntPtr , IntPtr ) at Gtk.Application.gtk_main() at Gtk.Application.gtk_main() at Gtk.Application.Run() at Gnome.Program.Run() at Tasque.Application.StartMainLoop() at Tasque.Application.Main(System.String[] args) Initially perhaps a more informative error could be displayed. Then, further down the line if possible, proxy support could be added?
Okay, well the crash is certainly bad. But I *think* Tasque should follow your GNOME proxy settings. Is this not working?
Hi Sandy, Thanks for the reply. I just using the system-wide proxy and it did not seem to work with Tasque: I received the same error message. (Firefox on the other hand did begin using the proxy settings immediately). Getting it to work with the Gnome Proxy settings would be great. It would still be very useful to be able to specify proxy settings *just* for Tasque. That way a proxy doesn't necessarily have to be used for all other applications which may not need it.
Hi, currently (version 0.1.8) Tasque seems not crashing anymore (this is good!) when attempting to contact RTM if RTM is not available (error 407 - proxy not authorized). If launched from shell, it keeps trying to contact server apparently forever (this maybe is not really good), while the UI does not say anything (this is definitely no good, if I hadn't tried launching from shell I wouldn't have known that). My system is behind a proxy, configured with Gnome Proxy settings, and more or less everything works, but I can't understand which configuration Tasque/RTM uses, if I set from shell http_proxy variable and then from the same shell I lauch Tasque, it doesn't work, still 407 error.
Sorry for the spam. Setting milestone to 0.1.11 aka "Enhancements Release"
Beware! New wave of spam! Changing severity to enhancement.
Tasque is not under active development anymore and has not seen code changes for five years, and both its mailing lists have seen their last activity three years ago at https://mail.gnome.org/archives/tasque-list/ and https://groups.google.com/forum/#!forum/tasky Its codebase has been archived: https://gitlab.gnome.org/Archive/tasque/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.