Re: lock request returns "405 Method Not Allowed"

Ben, thanks for your help. I have posted a request for help in the Apache HTTP SERVER USER forum.
  I hope somebody with knowledge get to read it, although it's a low traffic forum compared to this one.
  If and when I get a fix I'll make sure to share the info with this forum.
   
  Costa.

Ben Collins-Sussman <sussman@red-bean.com> wrote:
  Costa, these apache traces don't show us anything useful. Here are
the crucial two lines:

read(12, "writev(12, [{"HTTP/1.1 405 Method Not Allowed\r"..., 225}, {"HTML PUBLIC \"-//IETF//"..., 334}], 2) = 559

Apache reads the LOCK request from filedescriptor #12 (which is the
network socket from the client), and then we immediately see it write
a 405 response back to the socket.

From this, we can conclude that apache's response is based entirely on
a misconfigured httpd.conf; all the behavior that's causing the
response is entirely internal to apache's logic. It has nothing to do
with apache's inability to interact with its runtime environment. And
this is what we've been saying from the beginning. :-)

It's gotta be your httpd.conf that's disallowing LOCK requests. Somehow.

 
---------------------------------
Want to start your own business? Learn how on Yahoo! Small Business.
Received on Fri Mar 2 12:45:05 2007