[jdev] Incorrect Encoding

JD Conley jd.conley at coversant.net
Wed Nov 15 10:45:42 CST 2006


It looks like Google is requiring the initial response be sent. See
section 6.2 in RFC 3920.

 

-JD

 

From: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] On Behalf
Of ARP
Sent: Wednesday, November 15, 2006 8:25 AM
To: Jabber software development list
Subject: [jdev] Incorrect Encoding

 

Hi Guys,

 

Well, I am trying make a auth in talk.google.com, but I am having some
problems.

 

When I receive from the server:

 

<?xml version="1.0" encoding="UTF-8"?>
<stream:stream from="gmail.com" id="CC83300E366C0B75" version="1.0">
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
<stream:features>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>
PLAIN</mechanism>
<mechanism>
X-GOOGLE-TOKEN</mechanism>
</mechanisms>
</stream:features>

 

I answer with:

 

<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="PLAIN"/>

 

But the server sends to me:

 

<failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<incorrect-encoding/>
</failure>
</stream:stream>

 

Why this is happening ?

 

Please give some help

 

Thx

Alexandre

Brazil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20061115/9acb9820/attachment-0002.htm>


More information about the JDev mailing list