Forum Moderators: phranque
I'm digging around the tools here and found the Server Response tool. Cool!
Most of my sites seem to be fine, but one.
I get this "Status: HTTP/1.0 400 Bad Request" result and am trying to figure out what it means.
Could this possibly be of some significance to ranking, spidering or other things pertaining to good SEO/SEM practices?
Bruce Clay's Header Check seems to say things are fine with this site.
Thanks,
Chew
4xx Client Error = 400 Bad Request
The request contains bad syntax or is inherently impossible to fulfill
Client errors are generally issued by the webserver when a client tries to gain access to a protected area using a bad username and password
or
perhaps because you've typed an illegal character, or put in too many slashes (///).
I did not enter any bad chars that I know of - just the plain old URL.
C.
You might want to check your site access policies. The server header checker does not provide a user-agent or a referer, IIRC, and your site may disallow access if both of these request parameters are missing. However, the expected response would be a 403-Forbidden, so this is curious.
Jim
I would, if I knew how, and if there was a clue that this actually matters....
(maybe I'm not giving enough information?)
Please - can anyone indicate if this might possibly have a negative affect on ranking, linking, spidering, etc?
(maybe I posted this in the wrong forum?)
Site access policies are a mystery - yet another reason to change hosts.
The host's flavor is WebSitePro/2.5.4 if that is any help.
C.
Well, it's not likely your site has any access policies if you did not set them up.
Could this problem cause trouble with search engines? Maybe, but we don't know what "this problem" is, or even if it is a problem.
If you have access to your raw server access logs and error logs, take a look and see of you can find the request from the server header checker access and see if there were any associated errors.
Best,
Jim
