Forum Moderators: phranque

Message Too Old, No Replies

Precondition Failed - Apache error

Simple blog triggers a Precondition Failed

         

phishin4dmb

11:18 am on Dec 30, 2005 (gmt 0)

10+ Year Member



Ok my blog gets a Precondition Failed just about every time I visit it. other people get it too. Some times it happens sometimes it doesent. If I restart my server then it works fine for the first few times, then it displays the Precondition Failed error page.

I have searched the web and no ovbious answers. Any ideas on what would be causing this? The web site is accsing everything local.

[li2-102.members.linode.com...]

is a RSS feed I want to have my site acces as well as yahoo. or even

[li2-102.members.linode.com...]

Help please

Sincerely
Steve

jdMorgan

1:39 pm on Dec 30, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



From RFC 2616 [w3.org] Hypertext Transfer Protocol -- HTTP/1.1 :
10.4.13 412-recondition Failed

The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.

You'll need to investigate what request headers your browser is sending, and evaluate them in the context of what methods and features your server supports.

The most likely possibility here is that your browser is requesting something that your server is not configured to handle, such as a conditional GET, compressed content, or an unsupported or misconfigured MIME-type.

Check your raw server error log, and use the server headers checker and the browser headers checker at www.searchengineworld.com/misc/tools.htm or similar tools to check this out. You (and we) will need this information in order to figure this out.

Jim

phishin4dmb

2:42 pm on Dec 30, 2005 (gmt 0)

10+ Year Member



Jim:

Thanks for the info, i got it figured out. My server was running under a depericated Apache user. Since it was my server accessing my server it registered it as a bot. hence the error.

I simply changed Apache to run at a root uses which fixed the problem till I can fix the apache user group. Thanks for the help

Steve

jdMorgan

2:52 pm on Dec 30, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Glad to hear that! This sounded like it could have been a very tough problem, worst-case, if you had a bunch of complex scripts running, or content-control- related problems, and only an intermittent error...

Jim