On Mon, Jun 16, 2003 at 11:32:13AM +0100, Ben wrote: > Hi, > > I'm having a nasty HTTP implementation mismatch. > > Some server I'm talking to using LWP (I can't tell what the server actually is, > and Netcraft don't know either) is returning a 501 to a POST, not sending any > response body and then closing the connection. (As a side effect, this is causing > a segfault somewhere down in the XS code, but I think I understand how to > workaround this and will isolate the cause and try and patch it later). > > Now, I know that a 501 SHOULD contain a response body, but that's kind-of not > relevant. What I want to know is what server conditions could cause it to > think that a 501 is an appropriate thing to send back. > > I know that Not Implemented could apply to a request method or a transfer-coding > but are there any other examples that people know of that could trigger this? >
Hi Ben, Are you setting the Referer correctly for those pages? I have known people have PerlTransHandlers that try to detect scrapping and return errors based that. As far as a lot of companies are concerned if it only works with IE that is perfectly acceptable. Best bet it to browse it while capturing the datastream. Then you really know what it will accept rather that what you thought it needed. Then you can backout to a minimum data request. Hope it helps Paddy
