GlebkaF

sessionExpired in current version (basically since 3.19.5) can only return err.message = 'Not Logged In!'. It could be fired on any error before this commit.

Upgrading the module should solve the problem.

 

Also (as always):

Yeah, but for example:

• if we get "HTTP 401 error" when creating offer it means that cookies expired
• if we get "HTTP 403 error" when accepting offer it also means that cookies expired

Just thougth that there are some interpretation for this error also.

I'm not sure, but seem like this: usually, but not always occurs when i'm trying to create trade offer or accpet incoming offer. Sometimes it's happening for no apparent reason, after the next pooling.

Hi guys, can you tell me what exactly following errors means? I get them in sessionExpired callback:

• Error: HTTP error 504
• Error: HTTP error 503
• Error: HTTP error 502

Is there any difference between them? I'm asking, because it seems to me that sometimes when I got this 'sessionExpired' event session is don't really expired. Thanks