webpage has a redirect loop: chrome - google-chrome

I am facing a problem whenever I try appearing for a test in gateforum online test series. It used to work properly but now i am facing an issue. The whole account works properly except the one portion, As soon as I try to open tests , it shows an error in chrome saying the webpage has a redirect loop, I cleared all the cookies and cache, reinstalled chrome , still getting it. Also, I tried to use firefox browser, it also shows an error saying cookies might not be enabled , only if particularly tests button it clicked. Just to mention I checked for the cookies in firefox, there is no issue regarding it and cleared them there also, but not able to solve it. It would be really helpful if anybody could help.

Related

Firefox console getElementBy doesn't work

Can someone tell me why when i run
document.getElementsByTagName('img')[0]
in chrome's console shows what I want and doing the same on firefox does not?
After some research I found out I was doing it totally wrong as I would have to load the iframe first and then access it. I wrongly thought that this would be done automatically by the browser.

Figwheel working on Firefox but not on Chrome

The same application that I am developing works fine on Firefox but not on Chrome.
My application a day ago printed some things on the console, but I removed them today, which means that the actualized version of the application does not print anything on the console.
On Firefox it works, everything renders and there is not prints on the console.
However on Chrome, the app still prints on the console. It means that it is retaining some old state for some reason.
Does that even make sense? The code is already gone (erased), so the only way Chrome is printing the old state on the console is if he is storing it.
On Chrome I also get errors of undefined functions, but they are defined. On Firefox that does not happen.
Have you tried reloading the page? Another thing to try to really get rid of the state that the browser is obviously holding onto is to clear the browser cache.

Drupal 7 Chrome Login loop

After completing the installation of Drupal , I clicked on "view my website".
Chrome even though I sign in correctly it stays in the login page and the admin
bars are not visible.
Safari works , and as i checked the login attempts though Chrome are valid.
I cleared cache , I fixed tables #phpmyadmin and comment out the #cookie domain.
I am not sure how to check if the system time is off , or if this is actually the problem.
Thx a lot in advance
Open a Chrome incognito window and try that, it seemed to work for me. Due to Chrome's overly aggressive caching, this was the only thing that worked for me. I'm still unsure as to root cause of the problem.

Webpage displayed in Incognito, not in regular Chrome

So i have been running into this problem with a lot of Wordpress sites lately, usually occurring when i am logged in as Admin, so i couldn't post here because no one would be able to view the problem. However, i just found a site that it happens on that doesn't require admin creds.
http://www.otisports.com/
When i visit this site in Chrome (Version 34.0.1847.137 m), it just displays a blank page. No errors, just the (what now seems standard) event.returnValue is deprecated. Please use the standard event.preventDefault() instead. warning. I have seen that warning signify problems on the site, but they are usually minor, not to the extent that the above URL displays. However, if i open an Incognito window and visit the site everything works perfectly and there is no warning. Does the Incognito window deal with webpages in a way that is so entirely different that it would cause something like this to happen?
I have been racking my brain trying to figure this out. Can anyone reproduce this? is it a bug in chrome?
EDIT: I just tried to open a bounty on this question and the EXACT same thing happened. In Regular Chrome, nothing happened when i clicked the start a bounty link and i saw various errors Undefined is not a function however in incognito everything worked perfectly. what gives?!
EDIT: Yes, i have cleared the cache, history, cookies, everything, and i still get the same errors. I cant even post a comment on this question because of errors...
I came across the same issue when trying to open evernote.com. It loaded successfully while using incognito mode in chrome. Let me share how I fixed this even though the original post is way too old. But maybe someone can find it useful.
I'm using chrome (Version 73.0.3683.103 (Official Build) (64-bit)) running on Linux Ubuntu 18.04.2 LTS.
I tried disabling all extensions and clearing browser data/cache but nothing worked. PS: Disabling adblock previously worked for me. Yes, I stumbled over the same issue before and whitelisting evernote in adblock solved the issue. But it didn't now.
The following is what worked for me:
Open developers tools (CTRL + SHIFT + J).
Navigate to Applications tab.
Choose Clear storage from the side menu
Hit Clear site data button.
After reading the comments I dug into chrome and saw there was a bunch of extensions still sitting around that were definitely malware and I thought I had previously deleted. Instead of picking through them one-by-one, I just deleted everything, re-installed Chrome, and now everything works great!
I had the same issue. My application was working in Incognito mode and in Firefox but not in Regular Chrome. I even disabled all the extensions but no luck. I eventually cleared the Cached images and files because on developer console I found out that the regular chrome was still picking up the old file due to caching. So as soon as I cleared it, my app showed up like a rocket :)
Try removing any non required extension .
Specifically AdBlock
I resolved the problem post that.
Since on Incognito , extensions are disabled, hence page run as expected.
I resolved this unforeseen issue using following steps.
CTRL + SHIFT + DEL > Clear Browsing Data.
Cookies and other site data
Cached images and files
This is for Chrome Browser.
Open Console (Ctl+Shift+I) first.
Then under the application tab, you will find some options on the left, find out the application there, you will find it at the top.
There you will find Service Workers.
Under Service Workers, there will be three checkboxes. Select Update on reload checkbox and reload again.
I had the same issue after installing React-Sight Extention.
The Page hanged but not in the incognito mode.
Try deleting any recently added or junk extension.
Delete your cache.
That worked for me
I had a similar issue in chrome, in my case the problem was that I could log in to my university library's website only in incognito mode. After some digging, I figured out that Google Translate extension was set to automatically translate any page. When I turned that off and instead selected never translate that specific page, it started working in the usual mode as well.
This is rather an old issue but still happens. None of the solutions recommended here and there did not solve the issue in my case.
I somehow noticed this is related with a -some kind of- corruption on the user profile.
This is how I solved it:
Close all Chrome browsers.
Open a Google page on Chrome.
Sign-out from Google (rigt click your profile picture on a Google page, not on the Chrome itself), and sign-in.
If this doesn't work:
Close all Chrome browsers.
Right click Chrome icon and select Google Chrome.
Delete your Google profile on the "select your profile" page.
Close Chrome.
Open Chrome, sign-in.
uBlock Origin was the culprit in my case. Once I allowed the site in uBlock Origin, pages loaded correctly in normal Chrome.

Chrome Console Bug When Debugging Javascript

Chrome console tells you what line in the parsed file JavaScript syntax errors are located. Every once in a while, when I click on the link to take me to see the actual code of where the error is, I get a blank screen in the console. If I open up the same page inside Firefox with Firebug, I can see the error code without any issues.
Is this a known error in Chrome? If so, are there any ways to remedy it?
Here is an official list of known issues with Google Chrome. It doesn't seem like that is one of the known issues. I would try again and see if it happens again.