cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

FIXED!!! WordPress Site returning an HTTP 2xx or 3xx status

Jump to solution

My hypothesis is that McAfee SiteAdvisor does not like Add-On domains. 

The problem may be that only TOP LEVEL Domains can be verified. 

I'm basing that on the following....   I was able to verify my top level domain after I did the following.

This worked for TOP LEVEL domain:

- 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

However, I tried the same steps for one of my add-on domains and I still go the error Site returning an HTTP 2xx or 3xx status response code in the header of 404 pages.

Just to be sure there were no residual effects from my WordPress Plugins, I deleted the site and installed completely from scratch (WP 3.1.3).  I deleted both the default plugins (askimet and Hello dolly)  and I renamed the .htaccess file to .htaccessold.  Then I requested a McAfee validation file.  I still got the error.  

The only sites I cannot validate with McAfee are Add-on domains.

An Addon Domain is a domain name that points to a different subdirectory on your account. This gives you the ability to make it look like an entirely different website.

My Sites:

ScottsIdeas   Top Level Domain - Verified with McAfee

ScottsWebTips add-on - Unable to Verify

Scotts2012gear add-on - Unable to Verify

Message was edited by: scotts2012gear on 6/19/11 12:58:41 PM CDT

Message was edited by: scotts2012gear on 6/19/11 1:41:25 PM CDT
1 Solution

Accepted Solutions
Highlighted

Re: FIXED!!! WordPress Site returning an HTTP 2xx or 3xx status

Jump to solution

Okay, just spent 30 min with my host and we figured it out.

For Sub-domains, we had to rename the .htaccess file in the top level domain folder AS WELL AS the .htaccess in the sub-domain folder.

I was then able to open a validation request and validate my sub-domain.

View solution in original post

4 Replies
Highlighted

Re: FIXED!!! WordPress Site returning an HTTP 2xx or 3xx status

Jump to solution

Okay, just spent 30 min with my host and we figured it out.

For Sub-domains, we had to rename the .htaccess file in the top level domain folder AS WELL AS the .htaccess in the sub-domain folder.

I was then able to open a validation request and validate my sub-domain.

View solution in original post

Highlighted

Re: FIXED!!! WordPress Site returning an HTTP 2xx or 3xx status

Jump to solution

There is another issue we need to consider... That is plugins and themes.   I de-activated all my plugins and requested verification using the default theme.

STEPS for TOP LEVEL DOMAIN

- 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

STEPS for SUB-DOMAIN

- Deactivate all Plugins

- Use the default theme TwentyTen

- rename the top level htaccess to .htaccessold

- rename the sub-domain .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 Top level domain .htaccessold to .htaccess

- rename the sub-domain .htaccessold to .htaccess


Highlighted
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 4 of 5

Re: FIXED!!! WordPress Site returning an HTTP 2xx or 3xx status

Jump to solution

If this is the solution to the problem, that's great. I'm still waiting for any kind of feedback from McAfee, but a request for information about this is at least in the pipeline now thanks to a very helpful contact within SiteAdvisor. I don't know if this solution will work for all the others who've posted with this question, but it may be that some of them at least will find this applicable. In which case, thank you for giving me something to help other people with. I see you've got 25 years' experience in hardware and software ... that sort of experience definitely helps when it comes to something like this. Not sure if the survival training helped, unless it's to do with keeping your head when things go wrong  🙂

Highlighted

Re: FIXED!!! WordPress Site returning an HTTP 2xx or 3xx status

Jump to solution

Hi Hayton,

Glad to help.  Sorry, took so long to respond.  I'm on vacation.   

I use WordPress quite a bit.  I would love to know if my scenario helps anyone else.   

Sincerely,

B.Rgds,

Scott

How Many Badges Can You Collect?
Ready for a little competition? Members like you are earning badges and unlocking perks for their helpful answers. Are you? Click here to find out.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community