On Thu, Jun 19, 2003 at 02:04:04AM +0100, Ben wrote:
> Ah, you see, this isn't a page which a browser would ever see. It's an
> application that I POST some XML to, and it gives me back another XML
> document based on what I send it. I have a document which describes how
> this thing is supposed t
On Mon, Jun 16, 2003 at 07:51:54PM +0100, Patrick Mulvany wrote:
> 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 k
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 t
On Mon, Jun 16, 2003 at 11:32:13AM +0100, Ben wrote:
> 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.
Are you able to access the CGI s
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 se
