← Back to context

Comment by Ferret7446

3 hours ago

> My favorite bit of Googleism: Go to any site you sign in with Google SSO and watch the URLs in the eight redirects it has to do before it signs you in. You'll see a "youtube.com" in there. Even on a Workspace account. Youtube.com is a load-bearing website in their core auth flows.

I assume that's just because they need to set a cookie on the YouTube domain in case you visit YouTube later on the workspace account, and not "load bearing"in the manner you insinuate

If the youtube.com 302 failed to itself 302 back to the next destination; because the site is down; would that not be load bearing?