Do other Google sites work normally after you log in, the problem is only with Drive?

It's worth checking your cookie settings just in case. See: Websites say cookies are blocked - Unblock them.

Yes. GMail works fine (downloads attachments) and Google Voice (download voicemail) seem to both work.

You can consider to use the Live Http Headers extension to check the location fields in the HTTP response headers to see what is happening.

See also:

• http://kb.mozillazine.org/The_page_is_not_redirecting_properly
• http://kb.mozillazine.org/Websites_report_cookies_are_disabled

If clearing cookies didn't help then It is possible that the cookies.sqlite file in the Firefox profile folder that stores the cookies got corrupted.

• rename/remove cookies.sqlite (cookies.sqlite.old) and if present delete cookies.sqlite-shm and cookies.sqlite-wal in the Firefox profile folder in case cookies.sqlite got corrupted.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

• Help -> Troubleshooting Information -> Profile Directory:
  Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder
• http://kb.mozillazine.org/Profile_folder_-_Firefox

I have installed the Live HTTP Headers extension. Is there something I should be looking for in the output? I have tried the second method (deleting cookies and .sqlite/shm/wal files) with no success.

Since we did not get it on this end could you please list or screen shot your Extensions please.

The usual have you updated or installed anything prior to this issue.

Is not listed here could you please supply version of Firefox and what OS are you using please.

Did this happen after a Microsoft update (please check update history date) ?

When the server sends a redirect response in the HTTP response headers to Firefox then this response contains a location header. If the website keeps redirecting to the same URL then you know something is wrong. You can also check if there are cookies send via the request headers.

Also make sure that you do not block the referrer (network.http.sendRefererHeader should be default on the about:config page).

Pkshadow here is my information.

OS: Windows 10 Windows Updates: No recent Windows updates before this started happening. Firefox: 54.0.1 64-bit (Just updated as I typed this and problem still happens) Browser Monitoring Software: None Installed Extensions: Live HTTP Headers

This is basically a fresh install of FireFox from a week or two back. My old install started doing this, so I uninstalled and deleted my profile. Then I did a fresh install and am still having the issue.

Just in case anyone missed it, If I use Chrome, I can download files from my Drive account. According to Google support team, there is no issue on their end since it works fine in Chrome.

I am generating the live headers now. There are a lot of them, so I am looking to see if there is one that is the most interesting to see vs posting them all.

Here are the relevant HTTP headers.

   https://pastebin.com/YJYzR7yx

I don't know exactly what to look for. The top line of each (the target I assume) changes somewhat, but this one:

   https://doc-0g-04-docs.googleusercontent.com/docs/securesc/ng2ajaf3v0045d5g6plcaqds4spklc79/b7g9k7tq5cquelsd5gvg9gadd4kg00uf/1499004000000/03489968091051652849/03489968091051652849/0B0tT3_X-iMNzd2t6bXU1YVJVZGs?e=download&nonce=8q33i017aia52&user=03489968091051652849&hash=pfnc9ejm3a3d65u5stjajee71uq5v6n1

seems to repeat a good number of times.

If you look at lines 17-22, it seems the server responds to a background request with a new URL. If you try that URL directly (copy/paste line 22 to your address bar and press Enter to load it), will your Firefox download it?

Now... you may need to do something to prevent public access (I didn't try it myself).

It looks to me that the server request to set an AUTH_xxxx cookie for the doc-0g-04-docs.googleusercontent.com domain that never seems to be send because the links are to docs.google.com

Using a direct link to that domain might work if there isn't a redirect involved.

Sorry for the late reply.

jscher2000,

I looked at line 22 of the paste bin and it is not a URL.

If you were referring to the URL on line 1, I tried that and still have the same problem.

cor-el,

Is there something I should try based on that information?

Jman006 said

I looked at line 22 of the paste bin and it is not a URL.

Looking it now, I think I meant 32 (lines 17-32, URL on line 32).

I tried line 32 and I am getting a forbidden response even when logged into drive.

   https://pastebin.com/BaYNyqV0

Just tried a fresh download request via the right click command, saved the new live http header data and tried the same type of url and got a content not found page saying what I requested was not on their server. I'm thinking these links are just temporarily generated or something.

It could be a Firefox setting we're just not thinking of. Or maybe it's an external factor. Could you try:

New Profile Test

This takes about 5 minutes, plus the time to test Drive.

Inside Firefox, type or paste about:profiles in the address bar and press Enter/Return to load it.

Click the Create a New Profile button, then click Next. Assign a name like July2017, ignore the option to relocate the profile folder, and click the Finish button.

After creating the profile, scroll down to it and click the Set as default profile button below that profile, then scroll back up and click the Restart normally button. (There are some other buttons, but I think those are still "under construction" so please ignore them.)

Firefox should exit and then start up using the new profile, which will just look brand new. If given the opportunity to enable extensions, please just skip those so we can avoid complications.

Does Drive work any better in the new profile?

When you are done with the experiment, open the about:profiles page again, click the Set as default profile button for your normal profile, then click the Restart normally button to get back to it.

No this did not fix the problem. I still get "The page isn't redirecting properly" page.