Not logged in. · Lost password · Register
Forum: agsXMPP SDK Support RSS
My bad code blew up.
Page: previous  1  2 
Avatar
Koterpillar #16
Member since May 2007 · 32 posts · Location: Russia
Group memberships: Members
Show profile · Link to this post
In reply to post ID 2553
Alex, I pointed that out some time ago. And there is a difference between StatusCode == Forbidden and Response == null: the first is a clear case of "Invalid password", the second just being timeout. So:
  1. catch (WebException we)
  2. {
  3.     if (we.Response is HttpWebResponse // this is also false when Response is null
  4.         && ((HttpWebResponse)we.Response).StatusCode == HttpStatusCode.Forbidden)
  5.     {
  6.         base.XmppClientConnection.FireOnAuthError(null);
  7.     }
  8.     base.XmppClientConnection.Close();
  9. }
nebohodimo IM developer
Avatar
Alex #17
Member since Feb 2003 · 4246 posts · Location: Germany
Group memberships: Administrators, Members
Show profile · Link to this post
added this to our working copy. It will be in SVN with the next check in.
I thought we could get rid of the Google X-TOKEN authentication, but there is still no SslStream in CF 3.5.

I am currently evaluating Bouncy Castle crypto for TLS on CF to get rid of the Google X-Token. But there are some problems with eJabberd servers.

Alex
Alexander Gnauck
AG-Software
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Page: previous  1  2 
Forum: agsXMPP SDK Support RSS