See here: Google drive just been replaced:
http://wccftech.com/google-launches-drive-file-stream/
and it broke Google Docs!
Even with every single possible interaction HTTPS exclusion listed in the exceptions from this page...I'm still get HUGE loading times for Google Drive content...high file req times.
https://support.google.com/a/answer/2589954?hl=en
Lots of repetition... but even with this and every box checked for 'Skip these checks' it still chokes....
^https?://([A-Za-z0-9.-]*\.)?gstatic.com\.com/
^https?://([A-Za-z0-9.-]*\.)?google\.com/
^https?://([A-Za-z0-9.-]*\.)?google-analytics\.com/
^https?://([A-Za-z0-9.-]*\.)s\.ytimg\.com/
^https?://([A-Za-z0-9.-]*\.)?googleapis\.com/
^https?://([A-Za-z0-9.-]*\.)?googleusercontent\.com/
^https?://([A-Za-z0-9.-]*\.)?googledrive\.com/
^https?://([A-Za-z0-9.-]*\.)?ggpht\.com/
^https?://([A-Za-z0-9.-]*\.)?appspot\.com/
accounts.google.com
accounts.gstatic.com
accounts.youtube.com
clients1.google.com
clients2.google.com
clients3.google.com
clients4.google.com
commondatastorage.googleapis.com
cros-omahaproxy.appspot.com
dl.google.com
dl-ssl.google.com
gweb-gettingstartedguide.appspot.com
m.google.com
omahaproxy.appspot.com
pack.google.com
safebrowsing-cache.google.com
safebrowsing.google.com
ssl.gstatic.com
storage.googleapis.com
tools.google.com
www.googleapis.com
www.gstatic.com
chrome.google.com
clients2.googleusercontent.com
lh3.ggpht.com
lh4.ggpht.com
lh5.ggpht.com
lh6.ggpht.com
mtalk.google.com
^https?://([A-Za-z0-9.-]*\.)?google-analytics.com\.com/
ssl.google-analytics.com\.com/
^https?://([A-Za-z0-9.-]*\.)?ssl.google-analytics.com\.com/
docs.google.com
^https?://([A-Za-z0-9.-]*\.)?docs.google\.com/
^https?://docs.google\.com/
^([A-Za-z0-9.-]*\.)?accounts\.google\.com/
^([A-Za-z0-9.-]*\.)?docs\.google\.com/
^([A-Za-z0-9.-]*\.)?drive\.google\.com/
^([A-Za-z0-9.-]*\.)?googledrive\.com/
^([A-Za-z0-9.-]*\.)?plus\.google\.com/
^([A-Za-z0-9.-]*\.)?sheets\.google\.com/
^([A-Za-z0-9.-]*\.)?slides\.google\.com/
^([A-Za-z0-9.-]*\.)?talk\.google\.com/
^([A-Za-z0-9.-]*\.)?apis\.google\.com/
^([A-Za-z0-9.-]*\.)?googleapis\.com/
^([A-Za-z0-9.-]*\.)?googleusercontent\.com/
^([A-Za-z0-9.-]*\.)?video\.google\.com/
^([A-Za-z0-9.-]*\.)?gstatic\.google\.com/
^([A-Za-z0-9.-]*\.)?c\.docs.google\.com/
^([A-Za-z0-9.-]*\.)?script\.google\.com/
^([A-Za-z0-9.-]*\.)?gg\.google\.com/
Note that on the bottom of the page it now says:
Drive File Stream proxies
Drive File Stream encrypts all network traffic and validates host certificates to protect against man-in-the-middle (MITM) attacks. If you deploy to a network that uses a decrypting proxy, you may need to start Drive File Stream with this option:
--trusted_root_certs_file=<path>Path to a file containing trusted root and intermediate certificates. Must be in Privacy Enhanced Mail (PEM) format.
This thread was automatically locked due to age.