WordPress.org

1. scotte68
   Member
   Posted 11 months ago #

   I've spent hours researching this. Please do not refer me to links that I have already read and tried. I also have a request submitted to McAfee Support Forum: (McAfee Link)

   Please, does anyone has any new suggestions or Ideas.

   The McAffee Site Advisor does not recognize 404 HTTP headers when there is a WordPress installation.

   FACTS:
   - I am able to get websites WITHOUT WP verified
   - Websites with WP get the following McAfee error "It appears that the Web site mydomain.com (or http://www.scotts2012gear) is returning an HTTP 2xx or 3xx status response code in the header of 404 pages. "
   - These WP web sites all have proper 404 pages, ie.

   WHAT I HAVE TRIED:
   - I tried renaming .htaccess to .htaccessold and re-submitting (failed)
   - I tried the suggestions from this link (404 pages)
   I added the following to my header.php but they did not work :
   <?php header("HTTP/1.1 404 Not Found"); ?>
   <?php header("Status: 404 Not Found"); ?>
   <?php ob_start(); ?>

   - Downloaded CURL and checked the results:
   C:\CURL>curl -s-D - -o /dev/null http://www.scotts2012gear.com/no-one-here.html

   The CURL results clearly show that a 404 NotFound is returned.

   HTTP/1.1 404 NotFound
   Date: Thu, 16 Jun2011 02:56:05 GMT
   Server: Apache
   X-Powered-By:PHP/5.2.17
   X-Pingback: http://www.scotts2012gear.com/xmlrpc.php
   Expires: Wed, 11 Jan1984 05:00:00 GMT
   Cache-Control:no-cache, must-revalidate, max-age=0
   Pragma: no-cache
   Last-Modified: Thu,16 Jun 2011 02:56:06 GMT
   Vary:Accept-Encoding
   Transfer-Encoding:chunked
   Content-Type:text/html; charset=UTF-8

   Sincerely,
   B.Rgds,
   Scott

2. kmessinger
   Member
   Posted 11 months ago #

   Please do not refer me to links that I have already read and tried.

   How would we know what you have read or tried?

   Did you use this to check your site, http://www.siteadvisor.com/sites/domain/writeComments?firstTry=1&section=domainSuggestion

   It validates my wp sites with no problems.

3. scotte68
   Member
   Posted 11 months ago #

   Hmmm, well, I clearly listed what I have tried under the heading "WHAT I HAVE TRIED".

4. scotte68
   Member
   Posted 11 months ago #

   I have already tried....

   WHAT I HAVE TRIED:
   - I tried renaming .htaccess to .htaccessold and re-submitting (failed)
   - I tried the suggestions from this link (404 pages)
   I added the following to my header.php but they did not work :
   <?php header("HTTP/1.1 404 Not Found"); ?>
   <?php header("Status: 404 Not Found"); ?>
   <?php ob_start(); ?>

   - Downloaded CURL and checked the results:
   C:\CURL>curl -s-D - -o /dev/null http://www.scotts2012gear.com/no-one-here.html

   The CURL results clearly show that a 404 NotFound is returned.

5. scotte68
   Member
   Posted 11 months ago #

   I tried a Fresh install of WordPress 3.1.3 (ScottIdeas) and I'm getting the same error from McAfee Site Advisor. I have absolutely no plugins installed. I deleted "Hello Dolly" and "Askimet"

   I have already submitted a request to McAfee. I'm hoping someone else may have any insight into this bug.

   Sincerely,
   B.Rgds,
   Scott

6. scotte68
   Member
   Posted 11 months ago #

   I'm using the default Theme "Twenty Ten 1.2".

7. scotte68
   Member
   Posted 11 months ago #

   I finally got it to work. here is what worked for me.

   - Deactivate all Plugins
   - Use the default theme TwentyTen
   - rename the .htaccess to .htaccessold
   - Go Back to McAfee SiteAdvisor and click "Request Verification File"
   You should now see the McAfee Validation File name.
   - Create the file and upload to your host in the root directory
   - Go Back to McAfee SiteAdvisor and click the "Verify" Button
   - rename the .htaccessold to .htaccess

   Done. :)

8. kstadden
   Member
   Posted 7 months ago #

   THANK YOU scotte68 -- the .htaccess rename trick worked for me, and saved me hours of frustration.

9. scotte68
   Member
   Posted 7 months ago #

   kstadden,

   Glad to help. If you ever have a sub-domain, there is another fix for that. I had to rename the top level htaccess and the sub-level htaccess. Took me many hours to figure out the sub-domain fix. :d

   B.Rgds,
   Scott
   MaricopaMinutes

10. rainexpert
    Member
    Posted 2 months ago #

    Thanks. This worked for me too. Great Help!

Reply

You must log in to post.