CAAS and WS testers fail to connect to wss://tigase.im:5291 (#1100)

Closed

Activities

wojciech.kapcia@tigase.net opened 5 years ago

Trying to connect to wss://tigase.im:5291 from browser or using okhttp3.OkHttpClient (in CAAS test) yields code 400

$ curl https://tigase.im/.well-known/host-meta

<?xml version='1.0' encoding='utf-8'?>
<XRD xmlns='http://docs.oasis-open.org/ns/xri/xrd-1.0'><Link rel="urn:xmpp:alt-connections:websocket" href="wss://tigase.im:5291/" /><Link rel="urn:xmpp:alt-connections:xbosh" href="http://tigase.im:5280/" /></XRD>

wojciech.kapcia@tigase.net commented 5 years ago

There were two issues with this test

We were pointing our bosh to https://tigase.im:5280, which wasn't redirecting traffic anywhere (we are using https://tigase.im/bosh):
- trying to redirect address with bosh caused to change test request method from OPTIONS to GET (expected behaviour when using 302 redirection, one could use 307/308 but AWS doesn't support it) but because of #issue #1129 Tigase was hanging;
- trying to add target group that would handle connections on https://tigase.im:5280 resulted in similar problem - AWS on Application ELB requires health check monitoring, which periodically makes GET request which... again failed due to #issue #1129
On the other hand, when testing WebSocket CAAS test itself was missing WS headers - I created PR to include them https://github.com/iNPUTmice/caas/pull/73

Type	Bug
Priority	Normal
Assignee	wojciech.kapcia@tigase.net
Version	tigase-server-8.1.0
Spent time	4h

Child Issue

Parent Issue

tigase-private/Tigase Private#436 You are not authorized to access this issue

tigase/_server/tigase-http-api#76 Closed

Standardise DNS webservice to XEP-0156
#1129 Closed

BOSH timeouts on GET requests
tigase-private/Tigase Private#436 You are not authorized to access this issue

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#1100