Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

XEP-0156 (Discovering Alternative XMPP Connection Methods) #129

Closed
koehn opened this issue Mar 21, 2014 · 7 comments
Closed

XEP-0156 (Discovering Alternative XMPP Connection Methods) #129

koehn opened this issue Mar 21, 2014 · 7 comments
Labels
Feature

Comments

@koehn
Copy link

koehn commented Mar 21, 2014 •
edited by jcbrand

If I have properly set up a BOSH server and configured my DNS to serve up a URL per XEP-0156 (e.g., koehn.com), there's no need to use a third-party connection manager. The system could check the DNS for a TXT record at the XMPP host with text starting with _xmpp-client-xbosh and use that as the connection manager.

Trouble is I'm not sure how you do a TXT DNS resolution from the browser; you certainly could have a server-side component to do the discovery though, you'd just have to have a standard API to send the user's JID and get back the connection manager to use. The server-side component could get the domain of the JID, check the XEP-0156 DNS entries, and return either a default connection manager or the one used by the domain.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
@koehn
Copy link
Author

koehn commented Mar 21, 2014

Helluva nice library, by the way.

@jcbrand jcbrand changed the title Support XEP-0156 Support XEP-0156 (Discovering Alternative XMPP Connection Methods) Mar 24, 2014
@jcbrand
Copy link
Member

jcbrand commented Mar 24, 2014

Thanks. Would be nice if this could be done in the browser.

Here's an example of DNS in client-side JS: http://www.fileformat.info/tool/rest/dns-json.htm (not open source it seems).

@jcbrand jcbrand changed the title Support XEP-0156 (Discovering Alternative XMPP Connection Methods) XEP-0156 (Discovering Alternative XMPP Connection Methods) Apr 25, 2014
@devurandom
Copy link

XEP-0156 (Discovering Alternative XMPP Connection Methods) also specifies a pure HTTP discovery method.

@linkmauve linkmauve mentioned this issue Jul 14, 2018
Closed
linkmauve added a commit to linkmauve/converse.js that referenced this issue Aug 19, 2018
@linkmauve
WIP: Add support for XEP-0156.
0b11ce2 
It is disabled by default until more testing has been done, set
use_xep_0156 to true for now.

There is also the very big problem that the `Strophe.Connection` is
created before the user has had the time to enter their JID, which is
why we currently hardcode the domain to be resolved (this MUST be fixed
before this can be merged).  I haven’t been able to figure out where to
move this Connection creation, which must be after the JID is known but
before the actual connection is attempted.

There is also a bit of code duplication in it, this will be fixed in a
future version of this commit.

Fixes conversejs#129 and conversejs#1109.
@linkmauve linkmauve mentioned this issue Aug 19, 2018
Closed
linkmauve added a commit to linkmauve/converse.js that referenced this issue Aug 19, 2018
@linkmauve
WIP: Add support for XEP-0156.
e7350e6 
It is disabled by default until more testing has been done, set
use_xep_0156 to true for now.

There is also the very big problem that the `Strophe.Connection` is
created before the user has had the time to enter their JID, which is
why we currently hardcode the domain to be resolved (this MUST be fixed
before this can be merged).  I haven’t been able to figure out where to
move this Connection creation, which must be after the JID is known but
before the actual connection is attempted.

There is also a bit of code duplication in it, this will be fixed in a
future version of this commit.

Fixes conversejs#129.
Fixes conversejs#1109.
@jcbrand jcbrand added this to the 4.0.0 milestone Aug 20, 2018
@jcbrand jcbrand modified the milestones: 4.0.0, 4.0.1 Sep 7, 2018
@jcbrand jcbrand modified the milestones: 4.0.1, 4.0.2 Sep 22, 2018
@jcbrand jcbrand modified the milestones: 4.0.2, 4.0.3 Oct 3, 2018
linkmauve added a commit to linkmauve/converse.js that referenced this issue Oct 10, 2018
@linkmauve
WIP: Add support for XEP-0156.
36ed8dc 
It is disabled by default until more testing has been done, set
use_xep_0156 to true for now.

There is also the very big problem that the `Strophe.Connection` is
created before the user has had the time to enter their JID, which is
why we currently hardcode the domain to be resolved (this MUST be fixed
before this can be merged).  I haven’t been able to figure out where to
move this Connection creation, which must be after the JID is known but
before the actual connection is attempted.

There is also a bit of code duplication in it, this will be fixed in a
future version of this commit.

Fixes conversejs#129.
Fixes conversejs#1109.
@jcbrand jcbrand removed this from the 4.0.3 milestone Oct 11, 2018
jcbrand added a commit that referenced this issue Nov 18, 2018
@jcbrand
Initial support for XEP-0156. Updates #129
1328828
jcbrand added a commit that referenced this issue Nov 20, 2018
@jcbrand
Initial support for XEP-0156. Updates #129
ca97872
jcbrand added a commit that referenced this issue Nov 20, 2018
@jcbrand
Initial support for XEP-0156. Updates #129
7826c0c
@weiss weiss mentioned this issue Apr 9, 2019
Closed
@Neustradamus
Copy link

Any news about this ticket?
5 years old already!

@wiktor-k
Copy link

wiktor-k commented Apr 9, 2019

For the record XEP-0156 now recommends using CORS so that the host-meta file is discoverable from other domains and the Compliance Tester has been adjusted to check for CORS headers.

@poVoq
Copy link
Contributor

poVoq commented Aug 12, 2019

https://github.com/jsxc/xmpp-connection-discovery-node

jcbrand added a commit that referenced this issue Oct 10, 2019
@jcbrand
Initial support for XEP-0156. Updates #129
775d5e5
jcbrand added a commit that referenced this issue Oct 10, 2019
@jcbrand
Initial support for XEP-0156. Updates #129
91b9c88
jcbrand added a commit that referenced this issue Oct 10, 2019
@jcbrand
Initial support for XEP-0156. Updates #129
b31b2a7
jcbrand added a commit that referenced this issue Oct 11, 2019
@jcbrand
Fixes #129 Add support for XEP-0156.
6d9a638 
Only XML is supported for now.
jcbrand added a commit that referenced this issue Oct 11, 2019
@jcbrand
Fixes #129 Add support for XEP-0156.
91cc593 
Only XML is supported for now.
jcbrand added a commit that referenced this issue Oct 11, 2019
@jcbrand
Fixes #129 Add support for XEP-0156.
f04779e 
Only XML is supported for now.
@poVoq
Copy link
Contributor

poVoq commented Oct 11, 2019

Party!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

WIP: Add support for XEP-0156 linkmauve/converse.js
6 participants
@devurandom @Neustradamus @koehn @jcbrand @poVoq @wiktor-k