Thanks for the bug report. It has been forwarded to component maintainer.

Will be handled as an enhancement request instead.

https://garage.maemo.org/tracker/index.php?func=detail&aid=1369&group_id=164&atid=681

When I try and connect to a jabber server (on the LAN or externally) it
connects fine as long as I don't have a proxy server specified.  If I specify a
proxy server (I'm using squid 2.5) I cannot connect. Nothing shows in the squid
logs, and tcpdump -vvv | grep 5222 shows no communication between the n800 and
the jabber server.

I am running OS 4.2007.26-8 with the latest RTComm installed.

This also occurs on OS2008

slightly curious as to how you can classify a complete failure of a major part
of an "internet" device as an enhancement

Comment 7 Andre Klapper 2008-05-30 11:53:02 UTC

Chris H: 
The argumentation is that if there is no official document stating that http
proxy for jabber *must* be supported, then this is a feature request.
(please note that this is not my personal opinion.)

In 5.2008.43-7 (vanilla rtcomm), tcpdump shows it trying to connect to the
configured proxy host's TCP port 443 (https) instead of the configured port.

I ran netcat on the receiving end and saw the following request:

CONNECT (null):5222 HTTP/1.1
Host: (null):5222

So it looks like proxy connections are supported at some level in the stack,
but the right bits of data never make it there.

Created an attachment (id=1161) [details]
gabble/loudmouth debug output

If the connection to proxyhost:443 is refused, it falls back to un-proxied
XMPP.  Attaching debug output produced with "GABBLE_DEBUG=all LM_DEBUG=all
/usr/bin/telepathy-gabble".

Interesting bits (several bugs compounded):
> tp_cm_param_setter_offset: https-proxy-port = 443 = 0x1bb
[...]
> *** Connecting to: (null):5222
[...]
> Going to connect to proxy xxx.xxx.xxx.xxx:5222
> Trying xxx.xxx.xxx.xxx port 443...

Comment 10 Quim Gil 2009-05-18 22:41:14 UTC

Mikhail, can you comment on this old one please?

Comment 11 Mikhail Zabaluev 2009-05-19 14:09:33 UTC

I need to check the level of support for this in Loudmouth and Gabble.

Comment 12 Mikhail Zabaluev 2009-05-19 14:46:32 UTC

Support for CONNECT proxy does exist in Telepathy-Gabble via 'https-proxy*'
parameters of the connection manager. So the feature is half there.
We can consider integrating them with global proxy settings, but personally
I'll need to be enlightened as to how those are available to Fremantle
applications.

(In reply to comment #12)
> Support for CONNECT proxy does exist in Telepathy-Gabble via 'https-proxy*'
> parameters of the connection manager. So the feature is half there.

Yes, it just needs to connect to the gconf-configured proxy_https_port instead
of 443 (GABBLE_PARAMS_DEFAULT_HTTPS_PROXY_PORT) and send the correct XMPP
server hostname to the proxy.

Comment 14 Mikhail Zabaluev 2009-05-20 16:35:19 UTC

Will consider implementing in Fremantle.

Comment 15 Andre Klapper 2009-11-12 15:01:26 UTC

Can somebody retest this in Fremantle now that shipping of the N900 has been
started?

(In reply to comment #15)
> Can somebody retest this in Fremantle now that shipping of the N900 has been
> started?

In 1.2009.42-11 the proxy setting is ignored and it connects directly to the
server:

*** Socket library initialising...
*** Connecting to: (null):5222
*** Performing a SRV lookup for _xmpp-client._tcp.example.org
Going to connect to jabberserver.example.org:5222
Trying xxx.xxx.xxx.xxx port 5222...
Connection success (1).

and tcpdump confirms no attempt is made to connect to the proxy server
specified.

(In reply to comment #16)
> (In reply to comment #15)
> > Can somebody retest this in Fremantle now that shipping of the N900 has been
> > started?
> 
> In 1.2009.42-11 the proxy setting is ignored and it connects directly to the
> server:
> 
> *** Socket library initialising...
> *** Connecting to: (null):5222
> *** Performing a SRV lookup for _xmpp-client._tcp.example.org
> Going to connect to jabberserver.example.org:5222
> Trying xxx.xxx.xxx.xxx port 5222...
> Connection success (1).
> 
> and tcpdump confirms no attempt is made to connect to the proxy server
> specified.
> 

This bug was a major deal breaker for me on my N810, I had to use pidgin which
has better network proxy support. Now that i have pre-ordered the N900 I was
really hoping the issue would have been fixed. Seems all the Integrated IM
feature of the N900 would come to zero for does of us behind a network proxy :(

> This bug was a major deal breaker for me on my N810, I had to use pidgin which
> has better network proxy support. Now that i have pre-ordered the N900 I was
> really hoping the issue would have been fixed. Seems all the Integrated IM
> feature of the N900 would come to zero for does of us behind a network proxy :(

So maybe it's a good idea to vote for this bug to bring it into the mind of the
people who decide what features are implemented.

(In reply to comment #18)
> > This bug was a major deal breaker for me on my N810, I had to use pidgin which
> > has better network proxy support. Now that i have pre-ordered the N900 I was
> > really hoping the issue would have been fixed. Seems all the Integrated IM
> > feature of the N900 would come to zero for does of us behind a network proxy :(
> 
> So maybe it's a good idea to vote for this bug to bring it into the mind of the
> people who decide what features are implemented.

I have added my vote, am not used to bugzila so the voting process was not
really obvious to me. This bug would hinder lots of people using this device,
majority of use are students who are behind proxy firewalls :(

Tor for n900 is released: https://www.torproject.org/docs/N900
now supporting socks proxy is even more justified :)

Could someone please give an update to this bug? Is this gonna get fixed, do we
have to live with it? Any insight is highly appreciated. I can not use the IM
functions of my N900 with no proxy support. 

Thanks in advance.

Comment 22 Andre Klapper 2010-08-19 12:58:51 UTC

Proxy supprt was "not listed as a requirement in Fremantle planning" according
to Nokia. Currently it looks like a WONTFIX for Maemo5. Nokia has plans to fix
this for the version after Maemo5 ("Harmattan").

Comment 23 Andre Klapper 2010-11-20 22:52:36 UTC

The XMPP stack in Harmattan will support proxies as GLib 2.26 (which adds the
necessary proxy support) has been merged.

(In reply to comment #23)
> The XMPP stack in Harmattan will support proxies as GLib 2.26 (which adds the
> necessary proxy support) has been merged.

GLib would only add support for SOCKS proxies, which are barely used; the vast
majority of proxies are HTTP.

AFAIK HTTP proxies would be supported on wocky, not GLib, please check that the
version of wocky used in Harmattan would have this support.

Comment 25 Andre Klapper 2011-10-06 12:51:50 UTC

Nokia's internal "Communicate HTTP proxy settings to Gabble" bug report for
Harmattan has been closed as WONTFIX: There are no plans to officially support
this, sorry.