SAPISID Cookie not received

[UnitedMarsupials]

I'm using the patched version of the Hangouts-plugin -- with the fix for 429-errors already in. That problem does not bother me any longer, but this one keeps happening every once in a while:

(11:16:06) proxy: Connected to accounts.google.com:443.
(11:16:06) nss: SSL version 3.4 using 128-bit AES-GCM with 128-bit AEAD MAC
Server Auth: 256-bit TLS 1.3, Key Exchange: 255-bit TLS 1.3, Compression: NULL
Cipher Suite Name: TLS_AES_128_GCM_SHA256
(11:16:06) nss: subject=CN=accounts.google.com issuer=CN=GTS CA 1C3,O=Google Trust Services LLC,C=US
(11:16:06) nss: partial certificate chain
(11:16:06) certificate/x509/tls_cached: Starting verify for accounts.google.com
(11:16:06) certificate/x509/tls_cached: Checking for cached cert...
(11:16:06) certificate/x509/tls_cached: ...Found cached cert
(11:16:06) nss/x509: Loading certificate from /home/xx/.purple/certificates/x509/tls_peers/accounts.google.com
(11:16:06) certificate/x509/tls_cached: Peer cert matched cached
(11:16:06) nss/x509: Exporting certificate to /home/xx/.purple/certificates/x509/tls_peers/accounts.google.com
(11:16:06) util: Writing file /home/xx/.purple/certificates/x509/tls_peers/accounts.google.com
(11:16:06) nss: Trusting CN=accounts.google.com
(11:16:06) certificate: Successfully verified certificate for accounts.google.com
(11:16:07) util: Writing file accounts.xml to directory /home/xx/.purple
(11:16:07) util: Writing file /home/xx/.purple/accounts.xml
(11:16:08) http: Request 0x828729a00 performed without success.
(11:16:08) connection: Connection error on 0x828da97e0 (reason: 2 description: SAPISID Cookie not received)
(11:16:08) account: Disconnecting account xxxxxx (0x80f25ca00)

The solution is, in my case, to restart the tor-service, which I use for anything google (and some other sites).
Which leads me to believe, Google dislikes the particular tor exit point I happen to upon -- and, I'm sure, tries to tell me about it in an an error-message of some sort.

As a minimum, the plugin needs to relay such messages to the user. Verbatim... At the very least, the textual payload of any server response, that the code deems "invalid", needs to be logged. Better, perhaps, to show it in a popup...

[EionRobb]

The googlechat plugin has a slightly different way of logging in that doesn't use the same sapi cookie. Did you want to try with that plugin and see if it works over tor, instead?

[UnitedMarsupials]

Did you want to try with that plugin and see if it works over tor, instead?

Are you referring to Google via XMPP? I prefer Hangouts-mode, because it allows sharing pictures... I have both configured, but only Hangouts enabled -- and it usually works...

[EionRobb]

Oh, sorry, I mean with https://github.com/EionRobb/purple-googlechat I'm replacing the Hangouts plugin with it, since the Hangouts client is supposed to have been retired by now :)

[UnitedMarsupials]

Ok, I'll need to create a FreeBSD port of that first...

[UnitedMarsupials]

The googlechat plugin has a slightly different way of logging in that doesn't use the same sapi cookie.

Actually, whatever method it uses, I'm sure, Google will still treat some Tor exit-points with suspicion -- legitimate suspicion. There may also be other reasons for Google to reject a connection.

Whenever there is such a rejection, Google will generate, what your code will consider "invalid response". I think, any such unrecognized response should be displayed to the user -- rendered according to the specified mime-type (text/html, text/plain, whatever).