Not logged in. · Lost password · Register
Forum: Community Help and General Chat RSS
PSI + Google Talk + HTTP Polling

Announcement

2005-11-16, 20:33 by halr9000
Subject: Psi Groupchat (new address)
Join us at the Psi Groupchat (MUC)! Room name: psi@conference.psi-im.org
Page:  1  2  next 
pymehta #1
Member since Nov 2005 · 3 posts
Group memberships: Members
Show profile · Link to this post
Subject: PSI + Google Talk + HTTP Polling
Hello,

I am attempting to configure jabber for Google Talk, as it suports HTTP polling, which GAIM currently does not. The problem is after configuring it for GTalk server, it generates an invalid request for the proxy.

Configuration:
host: talk.google.com
port: 5223
Proxy type: HTTP Polling
Polling URL: I don't know (Empty)

Captured message through ethereal:

POST file:?server=talk.google.com%3A5223
...


The server responds as

HTTP/1.1 500 (The URL in invalide)
...


Is this a bug?
Avatar
halr9000 (Administrator) #2
User title: I work here
Member since Nov 2002 · 2315 posts · Location: Atlanta
Group memberships: Administrators, Members
Show profile · Link to this post
One of these should help:

http://psi-im.org/wiki/Google_Talk_HowTo
http://psi-im.org/wiki/Google_Talk_HowTo_for_Psi_0.9.3

Hmm I just realized we don't talk about http polling.  I assume you don't have a way to get port 5222/3 outbound?
Hal Rottenberg
Webmaster, Evangelist, Co-conspirator to the Revolution
IceRAM (Moderator) #3
Member since May 2003 · 1286 posts · Location: Bucharest, Romania
Group memberships: Global Moderators, Members
Show profile · Link to this post
Err... I have a feeling you really do need to enter something in the "HTTP Polling URL" field. This info can usually be found on the web page of the HTTP Polling service you want to use.
::/ my .net presence | psi
pymehta #4
Member since Nov 2005 · 3 posts
Group memberships: Members
Show profile · Link to this post
    I guess it is not gonna work for a while. I am behind a firewall which allows 443 but not 5223. Google Talk manages to do away with 443 only. I think the problem is due to lack of "STARTTLS" command support. I am not able to figure out how to get around it. I came across the fact that "STARTTLS" is not expected soon on psi, so I need to look at something else :-J

Dare I ask if anyone knows of a jabber client which will do "STARTTLS" for me till psi starts supporting it?

Thanks.
This post was edited on 2005-12-02, 15:02 by pymehta.
Avatar
Kev (Administrator) #5
User title: Project Lead
Member since Nov 2002 · 3085 posts · Location: Exeter, UK
Group memberships: Administrators, Developers, Members
Show profile · Link to this post
Gaim does, I believe.
Psi Project Leader 2004-08 - 2009-03. Blog
Like XMPP? Get the book!
IceRAM (Moderator) #6
Member since May 2003 · 1286 posts · Location: Bucharest, Romania
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post #4
Quote by pymehta:
    I guess it is not gonna work for a while. I am behind a firewall which allows 443 but not 5223. Google Talk manages to do away with 443 only. I think the problem is due to lack of "STARTTLS" command support. I am not able to figure out how to get around it. I came across the fact that "STARTTLS" is not expected soon on psi, so I need to look at something else :-J
I have a feeling there's some confusion flying around.

Just to clear up some things:
1. Google Talk does not use 443 for IM, as far as I know. It uses 5222. 443 is most likely used for mail notifications or something similar (Google specific anyhow) - Google Talk HowTo
2. What is this SSL/TLS thing I keep hearing about?
3. HTTP Polling should theoretically create a HTTP connection to the polling server and use the polling url to send/receive packages to the jabber server. The HTTP Polling server would act like a tunnel connecting you and the jabber server (well, just like any other proxy server).
4. If it's only a port problem, you might also have success using a HTTP Connect Proxy server (not necessarily a HTTP Polling server) or any other proxy server working on the http/https default ports.
::/ my .net presence | psi
Avatar
machekku #7
User title: Crazy guy from Poland
Member since Jul 2004 · 891 posts · Location: Poland
Group memberships: Developers, Members
Show profile · Link to this post
In reply to post #4
pymehta: did You check port 80? I just checked and Google's server is listening on that port. However, if you have a transparent proxy in your network, it may be a problem.

IceRAM: We're not talking about HTTP Pooling, etc. We're talking about Jabber server listening on non-jabber ports.
Maciek "Machekku" Niedzielski
Psi developer
IceRAM (Moderator) #8
Member since May 2003 · 1286 posts · Location: Bucharest, Romania
Group memberships: Global Moderators, Members
Show profile · Link to this post
Quote by machekku:
IceRAM: We're not talking about HTTP Pooling, etc. We're talking about Jabber server listening on non-jabber ports.
You are not? Hmm... sorry then... I had a weird feeling this thread was about this. Never knew Google "speaks Jabber" on non-jabber ports... Well, I learn something new every day...
::/ my .net presence | psi
Avatar
machekku #9
User title: Crazy guy from Poland
Member since Jul 2004 · 891 posts · Location: Poland
Group memberships: Developers, Members
Show profile · Link to this post
Or maybe I misunderstood the topic of this thread. Anyway:
[ mniedzi1@mion ] telnet talk.google.com 80
Trying 216.239.37.125...
Connected to talk.l.google.com.
Escape character is '^]'.
<?xml version="1.0" encoding="UTF-8"?>
<stream:stream to="gmail.com" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams">

<stream:stream from="gmail.com" id="702715F3161FE698" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">

There are many servers that do this trick.
Maciek "Machekku" Niedzielski
Psi developer
IceRAM (Moderator) #10
Member since May 2003 · 1286 posts · Location: Bucharest, Romania
Group memberships: Global Moderators, Members
Show profile · Link to this post
Hmm... that's very nice of them. An undocumented feature.
So, we should understand that GoogleTalk:80 works only with TLS (aka StartTLS), doesn't it?
::/ my .net presence | psi
Avatar
Kev (Administrator) #11
User title: Project Lead
Member since Nov 2002 · 3085 posts · Location: Exeter, UK
Group memberships: Administrators, Developers, Members
Show profile · Link to this post
Yes, the only port Psi can connect is 5223
Psi Project Leader 2004-08 - 2009-03. Blog
Like XMPP? Get the book!
pymehta #12
Member since Nov 2005 · 3 posts
Group memberships: Members
Show profile · Link to this post
Just Let me sum up the investigation to clear any confusion.

A) I am behind a firewall. The CONNNECT command is blocked on firewall in general, but port 443 is (I guess only) open port.

B) To connect to jabber server, there are 3 ways of doing it
  1) Direct connection
  2) Connect through a proxy supporting CONNECT
  3) Behave like web browser and use http polling.
The third options, as the google replied, is not supported yet.

C) To use the second option, You can use ports 80 (HTTP), 443 (HTTPS), 5222 and 5223.
D) The port 5223 does not require "StartTLS" at this time, all others do.
E) Psi does not support StartTLS at this time.

Hence from A), C), D) and E) it follows that psi is not an option right now.
Avatar
infiniti (Administrator) #13
Member since Sep 2002 · 1561 posts · Location: California, USA
Group memberships: Administrators, Developers, Members
Show profile · Link to this post
Regarding B-3, it is possible to set up an external HTTP polling service.  This is essentially what Tonneru was designed for.  I don't know of a public Tonneru set up anywhere, but if you have access to a web server somewhere you might be able to set up your own.  Then just set Psi to use the URL to wherever you set up Tonneru.  But you need to understand web/system administration to be able to do this, so it is not a very useful recommendation.
-Justin
This post was edited on 2005-12-04, 22:40 by infiniti.
ajmas #14
Member since May 2006 · 4 posts
Group memberships: Members
Show profile · Link to this post
I came across this thread because I am also behind a firewall that prevents connecting to port 5222 or 5223. Also my own personal analysis indicates that this entry in the wiki is incorrect:

http://psi-im.org/wiki/Google_Talk_HowTo#The_official_clie…

The analysis is based on what I see when using a packet analyser. Google Talk will use port 443 for email notification on the host www.google.com (a connection is etablished but it is quickly closed), but it uses port 443 on host talk.google.com for jabber communication (stays established). From looking at communications Google Talk will attempt three connections on port 5222 on talk.google.com and when it fails will connect to port 443 on the same host.

The first packet seems non standard, and I am not sure what the content represents, where as the second is a standard stream opening tag:

<stream:stream to="gmail.com" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">

minus the doc type. The rest is clear text. I used the following packet analyzer for my tests:

http://analyzer.polito.it/

If you want to simulate the behaviour be sure to block off ports 5222 and 5223.
ajmas #15
Member since May 2006 · 4 posts
Group memberships: Members
Show profile · Link to this post
Subject: Google Talk server code update
Looks like we won't need to worry about what magic is happening on port 443. I have just got a reply on the jdev mailing list, at jabber.org (see thread 'Google Talk and Port 443') , that a change has been made to the Google Talk server code to make it more like port 5223, though we will have to wait a few days before the code is deployed. This is good news :)
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please note the verification code from the picture into the text field next to it.
Smileys: :mellow: :huh: ^_^ :o ;) :P :D :lol: B) :rolleyes: -_- <_< :) :wub: :angry: :( :unsure: :wacko: :blink: :ph34r:
Special characters:
Page:  1  2  next 
Go to forum
This board is powered by the Unclassified NewsBoard software, 20090606-dev, © 2003-8 by Yves Goergen
Current time: 2010-02-09, 08:28:33 (UTC +02:00)