Bug 21221 - Expose <host-unknown> during login as Auth_Failed
Summary: Expose <host-unknown> during login as Auth_Failed
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL: http://git.collabora.co.uk/?p=user/wj...
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2009-04-16 06:39 UTC by Will Thompson
Modified: 2009-04-28 05:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Will Thompson 2009-04-16 06:39:06 UTC
If you try to connect to (say) talk.google.com with a foo@bar.com JID, it gives you a <stream:error><host-unknown/></>. This branch exposes that as Authentication Failed for Telepathy purposes.

It also adds a regression test for handling <conflict/>, since I had to work around a Loudmouth bug and my first attempt regressed.

% git diff --stat master
 src/connection.c                   |   45 +++++++++++++++++++------
 tests/twisted/connect/test-fail.py |   62 +++++++++++++++++++++++++++++++----
 tests/twisted/gabbletest.py        |   17 ++++++---
 tests/twisted/ns.py                |    1 +
 4 files changed, 101 insertions(+), 24 deletions(-)
Comment 1 Guillaume Desmottes 2009-04-28 04:01:35 UTC
+1
Comment 2 Will Thompson 2009-04-28 05:58:04 UTC
commit 481acb3e9b846423410d7d679142f569739b3792
Merge: 4cc2eae 507aee1
Author: Will Thompson <will.thompson@collabora.co.uk>
Date:   Tue Apr 28 13:43:21 2009 +0100

    Merge branch 'connection-errors'
    
    Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>

 src/connection.c                   |   45 +++++++++++++++++++------
 tests/twisted/connect/test-fail.py |   62 +++++++++++++++++++++++++++++++----
 tests/twisted/gabbletest.py        |   17 ++++++---
 tests/twisted/ns.py                |    1 +
 4 files changed, 101 insertions(+), 24 deletions(-)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.