hey
i'm not sure of your favorite browser... but if it's firefox, i would
suggest you load a plugin called livehttpheaders (i think). this allows you
to see exactly what's happening between the browser/server so you can see
what's needed from the client side when you're attempting to create a
On Apr 22, 2009, at 3:11 AM, Aaron Naiman wrote:
Thank you for getting back to me.
Some parts of the HTTP spec are ambiguous and left to
implementation. In
this specific case, error 411 means the server is saying that you
are not
sending a necessary content-length header, which is required
Note that this 'expects' is fairly soft and does not go much further than
"Applications SHOULD use this field to indicate the transfer-length of the
message-body, unless this is prohibited by the rules... " with the transmission
rules (keep alive, chunked, etc) beeing the only exceptions overrul
Dear Keary,
Thank you for getting back to me.
Some parts of the HTTP spec are ambiguous and left to implementation. In
> this specific case, error 411 means the server is saying that you are not
> sending a necessary content-length header, which is required for POSt
> requests whether there is an
Note that this 'expect' is fairly soft
> -Original Message-
> From: Bjoern Hoehrmann [mailto:derhoe...@gmx.net]
> Sent: 21 April 2009 23:42
> To: Aaron Naiman
> Cc: libwww@perl.org
> Subject: Re: 'POST' method leads to "411 Length Required"
>
> * Aaron Naiman wrote:
> >$request = new H
