On Sat, Oct 3, 2009 at 8:07 PM, Jakob Schroeter <js@xxxxxxxxxx> wrote:
>
> Quoting Shashank Singh <shashank.sunny.singh@xxxxxxxxx>:
>
> Thanks for the encouragement :P
>>
>> It appears to me that gloox is not creating a secure socket for connection
>> on port 443. That should be the reason why talk.google.com:443 gives up
>> and
>> closes the connection.Shouldn't there be a SSL handshake on such a
>> connection before the server responds to the XML request string sent?
>>
>> I am no SSL expert and might be headed in a wrong direction
>> any ideas will be appreciated :)
>>
>
> Apparently they use legacy SSL connections on that port which are not
> officially supported by gloox. You may be able to get it to work using
> 1.0-rc1 setting ConnectionTLS as custom connection
> (ClientBase::setConnectionImpl()).
>
Thanks! It did the trick :)
>
> cheers,
> Jakob
>
>
>
> --
> gloox-dev mailing list
> to unsubscribe:
> send a message with subject 'unsubscribe gloox-dev' to
> minimalist@xxxxxxxxxx
>
--
Regards
Shashank Singh
Senior Undergraduate, Department of Computer Science and Engineering
Indian Institute of Technology Bombay
shashank.sunny.singh@xxxxxxxxx
http://www.cse.iitb.ac.in/~shashanksingh