403 Forbidden

Solving “headers already sent” warnings

Hi esmi,

Thanks for the link. Apparently I found that my website’s wp-config.php had a lengthy base64 codes at the top, and I removed it completely after referring to the link’s information and cross-referencing with other of my websites’ wp-config.php. Strange that this occurred. I’m puzzled …

Unfortunately, this solution still doesn’t work, whenever I key-in a ‘www’ versus a ‘non-www’ domain name =(

Strange that this occurred. I’m puzzled …

Oh dear – that sounds very much like a hack.

https://codex.www.ads-software.com/FAQ_My_site_was_hacked
https://www.ads-software.com/support/topic/268083#post-1065779
https://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/
https://ottopress.com/2009/hacked-wordpress-backdoors/
https://www.ads-software.com/support/topic/253495#post-1017842

Hi esmi,

I doubt it’s a hack. Instead, I suspect that my hosting provider has installed the “nginx” webserver recently, which resulted in this. The strange thing is that some of my clients’ website aren’t affected.

Would you have any other guesses to this issue?

Cheers,
Jason

p.s.: By the way, I notice that one of my client’s website wp-config.php often has an ‘insertion’ of base64 codes at the beginning of the file. Removing it solved the problem.

p.p.s.: I’m puzzled if wp-config.php ends with “?>” or not. My guess without “?>”, hacks might occur. Correct me if I’m wrong =)

On the contrary, the “nginx” webserver ISN’T the cause of this problem. Apparently, as far as I noticed, the wp-config.php file DIDN’T end with a PHP closure, i.e. “?>”, which could have resulted in a HACK.

I’ve closed the wp-config.php file with “?>”, and added a security level listed in .htaccess (see, https://www.wpsecuritylock.com/wordpress-security-tip-how-to-protect-the-wp-config-php-file/).

As for the “Warning: Cannot modify header information …”, in my case, WP had a conflict with one of the cached files in my web-hosting ‘tmp’ folder. That was immediately resolved by clearing out those unwanted cached files.

I’m feeling relieved that these are sorted. New problems = New solutions = New experiences learned

=)