Bug 16034

Summary:	Doesn't support proxies that need authentication (HTTP 407)
Product:	Telepathy	Reporter:	Anurag Mishra <mishra.anurag07>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	nicolas
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	23646
Bug Blocks:

Description Anurag Mishra 2008-05-20 03:20:35 UTC

I tried using telepathy, through Empathy as frontend to use VOIP functions.
However, the interface provided no place to specify proxy.

Telepathy doesn't seems to support proxy for IM, while most popular applications like Pidgin/Purple do.

Steps to Reproduce:
1. Install Empathy with related telepathy-gabble support behind a network requiring authenticated proxy 
2. Create a new account and try to login.

Actual Results:
Empathy is unable to connect to required protocol's network.

Expected Results:
Should connect to required network, and should offer a proxy dialog or use system settings.

Build Date & Platform:
Used PPA repository at http://ppa.launchpad.net/telepathy/ubuntu hardy main
Package: telepathy-gabble 0.7.6.1~ppa8.04+1

Comment 1 Simon McVittie 2008-07-29 07:37:34 UTC

Adjusting title.

Supporting proxies that need a username/password (HTTP error 407) will require the following changes:

* Gabble gains http-proxy-username and http-proxy-password parameters

* Either or both of:

  (a) Mission Control takes the configured GNOME proxy username and password, and passes them on to Gabble in the same way that the server and port are currently done

  (b) Empathy gains http-proxy-server, http-proxy-port, http-proxy-username and http-proxy-password parameters in the Advanced area of account config

(Ideally, in the long term, Gabble should be able to ask the UI to ask the user for a username and password interactively, but that's tricky D-Bus API work.)

Comment 2 Nicolas Dufresne 2010-10-05 12:45:59 UTC

Telepathy Butterfly (MSN) already supports SOCKS5 and HTTP Connect proxy with authentication. I'm working on adding HTTP Connect proxy to Wocky (while SOCKS5/4a/4 is provided by GLib 2.26 and newer).

I suggest we attach dependency to this bug for tracking. Contrary to what Pidgin do, Telepathy connection manager rely on system proxy settings only for now (which are optained using libproxy).

Comment 3 Felipe Contreras 2011-11-29 09:58:33 UTC

Correct me if I'm wrong, but GNOME 3 proxy settings don't have any fields to enter the authentication information, so Simon McVittie's option (a) is not currently possible.

Comment 4 Nicolas Dufresne 2011-11-29 12:11:49 UTC

(In reply to comment #3)
> Correct me if I'm wrong, but GNOME 3 proxy settings don't have any fields to
> enter the authentication information, so Simon McVittie's option (a) is not
> currently possible.

Simon comment was posted in 2008, Gnome 3 didn't yet exist to make proxy support worst.

Comment 5 GitLab Migration User 2019-12-03 19:17:45 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/9.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.