Yes, you should explicitly set the transfer encoding to chunked instead
of setting the content length to 0. I'm not quite sure why an
exception would be thrown on a content-length 0 though, if the
exception isn't explicitely stating "hey don't set the content-length
to 0" I think it might be worth sending in the stack trace so we can
check whether or not it should happen. It is definitely odd to specify
a content-length of 0 but I would have thought it allowable in some
situations.
Regards,
Adrian Sutton.
On Friday, June 6, 2003, at 09:58 PM, George Gastaldi wrote:
Hello !
I think this may be considered a bug:
When the content-length of a request is 0, an exception is thrown,
so I must explicitly change to chunked-transfer encoding. Is this the
right
procedure ? (BTW it's working fine. :) )
Thanks !
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
