[OAuth2] Enhance how expired or invalid access tokens are handled
With respect of ESoupAuthBearer (used mainly with CalDAV), the missing implementation of the e_soup_auth_bearer_update() could cause repeated requests with the invalid access token, which had been eventually aborted after many tries by libsoup with a runtime warning: "SoupMessage <pointer> stuck in infinite loop?" The change makes the access token expired in such case, which stops the cycle early and doesn't increase the error counter on the server. The GData authorizers didn't consider expiration time at all.
parent
42e54328
Please register or sign in to comment