Skip to content

PSA: If You Get a ‘Too Many Google Drive Redirects Error’ in Safari, Try This

2018 April 25
by RSS Feed

If you try to directly download files from Google Drive, you may see an error message that says there were too many redirects. It turns out that the Google Drive redirects error is caused by Safari’s new Intelligent Tracking Prevention (ITP). Here’s what you can do.

[macOS: How to Prevent Tracking in Safari macOS High Sierra]

Google Drive Redirects Error

The error message, which you can see below, happens because ITP blocks the authentication check between Google and services like Securly. Google’s official response:

It is a known Safari issue that Intelligent Tracking Prevention (ITP) can cause interruptions when a site uses an authentication service such as Google, which can lead to an error known as “Too many redirects”.

There are two methods to solve this problem. You can either temporarily turn of ITP, or try clearing the website’s data.

Clearing Website Data

  1. Open Safari > Preferences from the menu bar.
  2. Click on the Privacy tab in the window that appears.
  3. Click Manage Website Data.
  4. Search for the website you’re having a problem with, like or Then click Remove. This will probably sign you out of the website.
  5. If that doesn’t work, then go back and click Remove All to remove all website data. If that doesn’t work, follow the steps below.

Turn off Cross-Site Tracking

  1. Open Safari > Preferences from the menu bar.
  2. Click on the Privacy tab in the window that appears.
  3. Under Website Tracking, uncheck the box next to Prevent cross-site tracking.

Clearing website data is a temporary fix, and the Google Drive redirects error will most likely appear after 24 hours. Since preventing cross-site tracking is a privacy feature, I recommend only turning it off temporarily whenever you need to download a file from Drive.

[Google Finds a Workaround for Apple’s Intelligent Tracking Prevention]

Source link:

Leave a Reply

Note: You may use basic HTML in your comments. Your email address will not be published.

Subscribe to this comment feed via RSS