On Wed, 2016-06-29 at 08:56 +0200, Milan Crha wrote: > On Wed, 2016-06-29 at 08:19 +0200, Rudolf Künzli wrote: > > On Wed, 2016-06-29 at 08:09 +0200, Rudolf Künzli wrote: > > > > Host: apidata.googleusercontent.com > > > > User-Agent: Evolution/3.20.3 > > > > ... > > > > Authorization: Bearer ... > > > > > Hi, > so it's 3.20.3 evolution, using OAuth2. Did you configure the account > directly in the evolution, or through GNOME Online Accounts? > > Maybe I broke something that the [1] stopped working. See the commit > message [2] for the explanation. > > Bye, > Milan > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=735311 > [2] https://git.gnome.org/browse/evolution-data- > server/commit/?id=00a465670ef3d
It's 3.20.3 evolution and the account is configured through GNOME Online Accounts. The problem did show up within 3.18.5 and GOA too... I read the messages in the links provided above and I have to commit that I am lost a little bit. --- The workaround is to preload the SoupAuthManager with a pre-configured SoupAuth when using OAuth 2.0 authentication. This avoids the initial unauthorized HTTP round-trip. --- How do I preload the SoupAuthManager with a pre-configured SoupAuth ? Thanks for help Rudolf > _______________________________________________ > evolution-list mailing list > [email protected] > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
