We don't handle 403s on rooms gracefully #18
Labels
A-Invite
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Minor
Impairs non-critical functionality or suitable workarounds exist
T-Defect
erikj (IRC)Dave: We don't seem to be handling 403s gracefully
2:02:36 PM
as in, I am now stuck on the spinner because it got fonxed trying to get pushrules
[13:08] Arathorn kegan: matrix-js-sdk seems to tightloop on
[13:08] Arathorn https://matrix.org//_matrix/client/api/v1/rooms/!lEZougoyUxdyEUlrFY%3Amatri…imit=20&dir=b&access_token= net::ERR_NAME_NOT_RESOLVED run_xhr @ index.js:218
[13:08] Arathorn if i remove netaccess
[13:08] Arathorn e.g. by VPNing
[13:10] kegan the js sdk does not automatically retry scrollback
[13:12] Arathorn okay, so it must be being triggered by trying to infinite scroll when you have no net access
...also...
If i'm kicked from a room, i can still try to send to it. JS console stacks up with loads of:
Failed to load resource: the server responded with a status of 403 (Forbidden)
q.js:161 Uncaught M_FORBIDDEN: User @matthew:matrix.org not in room !OkPeYYmtiSfwzDbCsg:matrix.org (<FrozenEvent event_id='$14375444627737xXjLH:matrix.org', type='m.room.member', state_key='@matthew:matrix.org'>)
The text was updated successfully, but these errors were encountered: