16 messages in com.googlegroups.google-talk-openRe: Google Talk and Port 443
FromSent OnAttachments
Andre18 May 2006 08:37 
Paul Johnson18 May 2006 08:53 
Andre18 May 2006 09:52 
Paul Johnson18 May 2006 10:41 
Andre18 May 2006 12:37 
Andre Magalhaes18 May 2006 13:29 
Ruben Pedro19 May 2006 06:32 
Andre19 May 2006 07:42 
Ruben Pedro19 May 2006 11:46 
Andre20 May 2006 10:42 
Ruben Pedro21 May 2006 11:40 
Andre22 May 2006 08:00 
Ruben Pedro22 May 2006 08:37 
Andre26 May 2006 08:21 
Ruben Pedro26 May 2006 10:03 
Ruben Pedro26 May 2006 10:44 
Subject:Re: Google Talk and Port 443
From:Andre Magalhaes (andr@gmail.com)
Date:05/18/2006 01:29:33 PM
List:com.googlegroups.google-talk-open

Hi,

I also noticed that. I am a developer of Tapioca (see http://tapioca-voip.sf.net), and i did enabled the support for HTTPS connections, but this does not work when using google talk client. It works fine with other Jabber servers. I also noticed this dumb packet sent by GTalk client (that works), but i have no idea what it is. The GTalk server simply does not respond to the initial stream command, while other Jabber servers do. It seems this dumb packet is the answer for our questions.

BR Andrunko

On 5/18/06, Andre <andr@gmail.com> wrote:

Hi,

I have noticed a number of third party Jabber clients are having issues connecting to port 443 at talk.google.com. Does anyone know if there is something particular about the way Google Talk is handling data to that port?

Using a packet analyzer on Windows I see two packets at the beginning: the first with what looks like 'junk' data (not sure what it represents) and the second with the stream opening tag:

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

curiously there is no doc type header:

<?xml version="1.0"?>

All remaining packets are in plain text XML.

I have tried connecting to 64.233.167.125 with telnet on port 443. If omit the doc type header and simply add the stream tag then the connection is closed immediatly. If I add it the connection stays open a while and then closes with no response. I am suspecting that there is more in that 'junk' data than meets the eye.

BTW I also notice that two connections to anothe address show up with a TIME_WAIT status, when doing netstat:

72.14.207.104:https TIME_WAIT

If anyone can provide any insight it would be appreciated. Currently I amd behind a firewall and the Google Talk client is the only one which seems to be able to connection Google.

Andre