I went through the process of securing my admin area a little more and keep getting the Corrupted Content Error when I try to log in. My front end works great, but I can't get into my admin area. I changed the name of the index.php in my config file and uncommented. I also changed my admin folders name from couch. I also took the extra step of copying the _index.php file and renaming it index.php to give the hacker a form that never allows logging in. etc, etc. That's when the Corrupted Content Error came about. So I changed everything back to the way it was and still get this error.

[KK]

Hi,

One possible reason for the 'Corrupted Content Error' could be that the browser is getting into an infinite redirection loop.

If you could PM me the FTP+Couch creds to your site, I can take a look at the issue for you.

Thanks.

[trendoman]

Hi, jgpee and Welcome!

Does it happen in Firefox only? If so, then please try to clean up the browser's cache or use incognito mode. That will tell us if the problem is with old cookies or cached pages. /couch/cache also can be cleaned up if you had this setting in config.php. Did anything help?

Well after a little investigation I figured out that I was still using the index.php file for the fake login page. I ftp'd the original index.php file and now everything works great. I did notice that only Firefox threw the Corrupted Content Error. If I used the correct credentials in chrome, safari, IE, or Opera they all just reloaded with no error. But none of them said incorrect credentials until I actually entered incorrect ones. Either way, thanks for the help.

[trendoman]

But none of them said incorrect credentials until I actually entered incorrect ones. Either way, thanks for the help.

Welcome and thank you for sharing the outcome.

Does the quoted mean that on fake login page browsers say that credentials are incorrect only for the incorrect one and don't say anything for correct creds?

They didn't say anything. The page just reloads if I enter the correct credentials. I figured even though it's low risk, it could be a security issue if someone figures it out. Either way, if a good hacker wants to get into your backend, they'll do it regardless of what you may have to prevent it. But it's worth the extra effort to slow them down.