Google Drive 301 redirect problem in both Internet Explorer 9.0 and Google Chrome.
How to download and recover my documents back?
Error details:
The webpage at https://docs.google.com/nonceSigner?nonce=7cb3t4occcafo&continue=https://doc-14-bg-docs.googleusercontent.com/docs/securesc/i5n0sn4aobda0j320f46k73eteiillh3/plshk64l31ed2qevsqk23j88fdobcn2g/1342972800000/16921087564105121353/16921087564105121353/0B4IwZnOWxZeUMUdqOG9iU2dRT3VGMm82aDdWNUV3QQ?e%3Ddownload%26hash%3Dhhjr1n96p6fbnep6l9cudvmg5ec7jr43%26nonce%3Db1573nhruskb0%26user%3D16921087564105121353&hash=f23l5btt5380bvi1fh63om23i6m3t5t4 has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Here are some suggestions:
Reload this webpage later.
Learn more about this problem.
I have experienced this in Chrome, IE, and Firefox when trying to download files from Google Drive. Disabling extensions & incognito didn't solve this for me, but I was able to find a workaround by using the Google Drive Desktop app.
https://tools.google.com/dlpage/drive
Hope that helps!
Based on a hint on cookies on Google forums, I found a solution:
By allowing Google to set cookies, the problem disappeared for me. Chrome settings > Advanced > Content settings ... > Cookies > Manage exceptions. Allow:
https://[*.]google.com:443
https://[*.]googleusercontent.com:443
The rule could be more specific but this works. I hope this helps. I had non-default cookie restrictions.
Related
I need to disable Chrome's iframe security for just one page so that I can access the contents of cross-domain websites.
I have complete control over this browser, this can use extensions.
I have been looking for a way to do this for the past hour or so. No luck.
You can try out this extension to bypass when development, this will allow you to resolve the issue with cross-domain issue:
https://chrome.google.com/webstore/detail/cross-domain-cors/mjhpgnbimicffchbodmgfnemoghjakai
Disclaim: I am the owner of this extension.
I have created a new website www.bucketshowers.com and I tried to index it using google webmaster tools. Fetch as Google for the desktop worked just fine, but doing the same for mobile shows an error "Temporarily unreachbale". It's been a few days and the website REALLY is not avaible on mobile. It's driving me nuts. Here're is some information and things I have already tried:
Website is made with WP
I have disabled all SEO/meta tags plugins and I added a very basic robots.txt http://bucketshowers.com/robots.txt
I tried waiting 15min between fetching the root page on mobile
I have checked source code for the homepage to make sure there are no meta tags with nofollow or noindex attributes
I baffled by this issue and I would gladly take any advise/pointers what else can be done. Thank you.
The crazy thing was, that it was caused by WP Statistics plugin, which is probably the most popular from its kind - 500k downloads. When I deactivated it, everything is fine, google fetches of the mobile and the website is available. Incredible! I'm still searching for the actual problem within that plugin.
I've been playing around with GitHub pages for a while, and have been doing most of my development in Firefox. Everything was working amazingly, until I attempted to test my project page in Google Chrome. To my surprise, when visiting the same GitHub project page in Firefox and Chrome, Firefox was served the correct index.html page while Chrome was served a completely different (and incorrect) one.
I've poked around for a few hours now and honestly have no idea what's going on. Both Firefox and Chrome are requesting the exact same URL with an HTTP GET request and receive different responses from the server. I've tried changed the user agent and messing with the request header in both browsers, and it didn't seem to affect anything.
Does anybody have a clue what's going on? If it helps, the project page in question is "https://wgxli.github.io/complex-function-plotter/". Any help is much appreciated.
Edit: It appears to be related to a browser cache issue. The behavior disappears if I clear all data from the browser and visit the above page. However, if I clear the browsing data, visit the root directory of the above page, and then request the above page, the problem reproduces itself. At this point, I think I've reduced it to a question of why the browser (or CDN) is returning a cache hit when it shouldn't.
I ended up fixing the issue. I was using create-react-app, which automatically registers a service worker for local caching. I just disabled this service, which resolved the problem.
I previously set a directory on my web server to require a username/password during development phase. I have since removed the .htaccess file to remove the password, I have also checked the cPanel to make sure there are no settings for a user/password.
Despite this, Chrome keeps asking for a username/password. If I click Cancel, the page continues to load anyway.
This only happens on Chrome Windows and Mac. I have cleared the entire cache for Chrome but to no avail. I am not able to replicate the problem on Firefox 4 or Internet Explorer 9.
I figured it out. I was silly enough to have left the URL pointing to a domain which does ask for a username/password but the domain it was pointing to was for the development site. Not sure why the other browsers didn't do the same thing but updating the base href has solved the problem.
I am having an SSL issue, but it only appears to be happening in Google Chrome.
I've checked with Firefox, Safari and Internet Explorer and there fine.
Does anyone know what is wrong? I've tried it on a BLANK page and Chrome still says there is an issue. Screenshot:
If anyone can help that would be much appreciated!
I think you may be referring to content that does not belong to your domain (ex. images) and that are retrieve from another location on the internet.
Since the browser has to get them via a http:// request on the other site, it warns you that all the content does not come from your website overs the SSL connection.
Did you tried the blank page after accessing another page of your site? Or just after launching chrome?
I run into this exact problem and solved it this morning. Two things:
Clear Google Chromes's browser cache data
Make sure your app doesn't have references to external resources that is none-https
Hope this helps,
Ray.