Wojciech Kapcia (Tigase) opened 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 usinghttps://tigase.im/bosh):- trying to redirect address with bosh caused to change test request method from
OPTIONStoGET(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:5280resulted in similar problem - AWS on Application ELB requires health check monitoring, which periodically makes GET request which... again failed due to #issue #1129
- trying to redirect address with bosh caused to change test request method from
- 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
- We were pointing our bosh to
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Version |
tigase-server-8.1.0
|
| Spent time |
0
|
Issue Votes (0)
Watchers (0)
Trying to connect to
wss://tigase.im:5291from browser or usingokhttp3.OkHttpClient(in CAAS test) yields code 400$ curl https://tigase.im/.well-known/host-meta