[jdev] Incorrect Encoding

Dave Cridland dave at cridland.net
Thu Nov 16 04:13:15 CST 2006

On Wed Nov 15 19:27:06 2006, Norman Rasmussen wrote:
> On 11/15/06, Norman Rasmussen <norman at rasmussen.co.za> wrote:
>> My guess this is a bug on Google's end.  I wonder if any of the 
>> google
>> guys would be able to confirm this.
> woops, my bad.  I thought Google's servers were totally wrong, turns
> out they just _require_ the SASL auth data when the auth mech is
> picked.

That's still a bug in Google's implementation, though. RFC4422 says 
that's optional, for both protocol profiles and mechanisms. (Section 
4, point 3a, and Section 5, point 2a).

RFC3920 doesn't mandate usage of an initial response either.

Of course, using the initial response facility makes sense if you 
can, since it always saves at least one round-trip.

Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at jabber.org
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

More information about the JDev mailing list