Standardise DNS webservice to XEP-0156 (#76)

Wojciech Kapcia (Tigase) opened 6 years ago

We currently have DNS Webservice to provide information about alternative connection methods. There is a dedicated XEP for this use-case ( XEP-0156: Discovering Alternative XMPP Connection Methods ) and we should either adapt DNS webservice to it.

Related
- CAAS and WS testers fail to connect to wss://tigase.im:5291 (tigase/_server/server-core#1100) Closed

Activities

Andrzej Wójcik (Tigase) commented 6 years ago

I've added this feature, checked that it works and added information about it to the project documentation.
Andrzej Wójcik (Tigase) commented 6 years ago

The only issue here is the missing support for X-Forwarded-For as current implementation ignores that header and users Host header which may differ.

As for only returning BOSH, it is OK as for domain which you checked (hostname of EC2 instance) there are no TXT records and its name is resolved to the internal address and resolved back to an internal DNS name. It works just fine for domain names with TXT records.

Would it be possible to add proxy_set_header Host $host to NGINX config file? as I think that is the missing part which would solve the issue and not missing support for X-Forwarded-For.
Wojciech Kapcia (Tigase) commented 6 years ago

Works correctly now. I added example nginx configuration to documentation.
Login to comment

Type	New Feature
Priority	Blocker
Assignee	Wojciech Kapcia (Tigase)
RedmineID	8577
Version	tigase-server-8.1.0

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-http-api#76