Next Question
RSS
4xx errors represent all HTTP errors starting with 4.
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
and so on.
Their occurrence is normal, I guess, don't worry about it.
Permalink | Report
400 Bad Request
The request contains bad syntax or cannot be fulfilled.
401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. See Basic access authentication and Digest access authentication.
403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
404 Not Found
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
06 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
Client failed to continue the request
409 Conflict
More Info found here:
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Is there a password protected area of your site, maybe bots are trying to hit that.
If you need any more information, or what me to analyse some of the possible errors drop by at www.wiredvillage.ca.
Good luck!
Source(s):
wikipedia.org
Permalink | Report
HTTP 4xx errors usually indicate that the server could not understand the request or cannot process it, the request was forbidden, or the request timed out. They also may indicate authentication error.
Source(s):
RFC2616
Permalink | Report
Permalink | Report
Fixing the problem depends on the referer. Possible solutions are:
- put in a redirect (if people have bookmarked old/moved pages)
- contact referring sites (if they are sending bad urls your way)
- fix your own content (if you've put in bad links)
- fix your content management system (if it's automatically putting in bad links)
- fix your sitemap (if you've registered one that contains bad links)
All of the above only apply to 404 errors. If it turns out the problem isn't 404 I'd suggest reposting with the exact error number from your log file.
Source(s):
http://en.wikipedia.org/wiki/HTTP_404
Permalink | Report
Answered Question
M$1
December 20, 2008 05:22 PM
What are 4xx HTTP errors in Google Webmaster Tools, in reference to a blog? (see details below)
I'm getting a boatload of HTTP errors on a blog of mine in Google Webmaster Tools. These are not 404 errors, they are described as 4xx errors. Can anyone advise as to what type of error this is, and how to best fix it.
Tip offered.
Tip offered.
Interesting Question?
Yes (0)
No (0)
RSS
Best Answer Chosen by Asker
| December 20, 2008 05:28 PM |
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
and so on.
Their occurrence is normal, I guess, don't worry about it.
| Asker's Rating: |
• Very helpful to me with a blog issue. Thanks Bugsy.
Permalink | Report
Other Answers (4)
December 20, 2008 05:29 PM
These are all the 400 series errors. So it includes 404s and 400, 401 etc. Here is a list more can be found at Wikipeida.org 400 Bad Request
The request contains bad syntax or cannot be fulfilled.
401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. See Basic access authentication and Digest access authentication.
403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
404 Not Found
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
06 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
Client failed to continue the request
409 Conflict
More Info found here:
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Is there a password protected area of your site, maybe bots are trying to hit that.
If you need any more information, or what me to analyse some of the possible errors drop by at www.wiredvillage.ca.
Good luck!
Source(s):
wikipedia.org
Permalink | Report
December 20, 2008 05:35 PM
RFC explaining all HTTP code can be found here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html HTTP 4xx errors usually indicate that the server could not understand the request or cannot process it, the request was forbidden, or the request timed out. They also may indicate authentication error.
Source(s):
RFC2616
Permalink | Report
December 20, 2008 07:10 PM
This simple means that when google bot tried to access that page of yours, it got an error. Now that error could be because the coding is wrong on that page, or your hosting server is down, or your URL is not search engine friendly. I'd suggest have a look at it and if you find error is ffrom your side, correct it ASAP.
Permalink | Report
December 20, 2008 10:33 PM
The first thing to do is take a look at your raw log files to find what the specific errors are. The most worrying would be if you're continually getting a 404 (not found) error on those urls. This would mean that you have broken links on your site, in people's bookmarks, or on sites pointing to you. You can find the source of this error by looking at the "referrer" in the log file - i.e. where your links are coming from. Fixing the problem depends on the referer. Possible solutions are:
- put in a redirect (if people have bookmarked old/moved pages)
- contact referring sites (if they are sending bad urls your way)
- fix your own content (if you've put in bad links)
- fix your content management system (if it's automatically putting in bad links)
- fix your sitemap (if you've registered one that contains bad links)
All of the above only apply to 404 errors. If it turns out the problem isn't 404 I'd suggest reposting with the exact error number from your log file.
Source(s):
http://en.wikipedia.org/wiki/HTTP_404
Permalink | Report
Answer this Question
Related Questions
Ask a Question
Buy Mahalo Dollars with Credit Card or PayPal
Top Members
Most Popular Tags
Categories
- Anonymous
- Arts & Design
- Beauty & Style
- Books & Authors
- Business
- Cars & Transportation
- Consumer Electronics
- Coupons Deals
- Education
- Entertainment
- Environment
- Fitness
- Food & Drink
- From Email
- From Iphone
- From Twitter
- Health
- History
- Hobbies
- Home & Garden
- How Tos
- Humor
- Jobs
- Legal
- Local
- Love & Relationships
- Mahalo Answers Community
- Money
- Music
- News
- NSFW
- Parenting
- Pets
- Science & Mathematics
- Services
- Shopping
- Social Science
- Society & Culture
- Sports
- Technology & Internet
- Travel
- Video Games
Welcome New Members
- ashley7237, November 26, 2009 09:07 PM
- ashley369, November 26, 2009 09:04 PM
- danodonnell, November 26, 2009 08:57 PM
- michaelhale, November 26, 2009 08:54 PM
- zaida, November 26, 2009 08:23 PM
Mahalo Dollars are the currency of Mahalo Answers.
Each Mahalo Dollar costs $1.
Once you earn more than 40 Mahalo Dollars, you can request to be paid via PayPal. Each Mahalo Dollar is currently worth $0.75 when paid out via PayPal. Learn More

http://www.google.com/support/forum/p/Webmasters/thread?tid=6bb12f9d43abd469&hl=en
In general, these errors are from attempts to access your site that failed with a 4xx result code (this is most frequently a 403). It looks like we ran into a bunch of these errors during the timeframe that you saw. If this was also the time when you changed your .htaccess file, it might be that they are related.
I would continue to keep an eye on these errors. If you do not see any more recent errors listed here, you can probably assume that the error has cleared itself up and that things will normalize soon.
"The blog that was implemented to your site against Google was actually
set up through a .htaccess file. This wiki article is actually a pretty
handy guide for blocking IPs that hit the site excessively, which if you
use the article to access your .htaccess file, you will then know how to
add and remove these blocks:
http://wiki.dreamhost.com/Finding_Causes_of_Heavy_Usage
The Googlebot block has since been removed, so you should be all set from
here! Let me know if you have any other question".
So i think (and hope) the issue is now fixed. Do i need to do anything else on my end as far with Google? Do i need to re-submit those pages.