You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Package: 0.15.9 class: HTTP.cs method: public async Task Request Conditions: using secure protocol only
Problem: In case of expired reconnection token, the error should return : "Reconnection token invalid or expired". But instead, it tries to use unsecure protocol and completely forgets about original error message and returns : " Unexpected end of JSON input".
It would be nice to have this fallback optional or the original error.
The text was updated successfully, but these errors were encountered:
Hi @guntarsbeetroot, thank you for reporting. This behaviour of switching from secure to insecure protocol must be removed soon. If you can send a PR I really appreciate it, I'll be able to check this out only next month I think.
Package: 0.15.9
class: HTTP.cs
method: public async Task Request
Conditions: using secure protocol only
Problem: In case of expired reconnection token, the error should return : "Reconnection token invalid or expired". But instead, it tries to use unsecure protocol and completely forgets about original error message and returns : " Unexpected end of JSON input".
It would be nice to have this fallback optional or the original error.
The text was updated successfully, but these errors were encountered: