W3C home > Mailing lists > Public > www-lib@w3.org > January to March 2001

Re: does HTPostAnchor() have problems POSTing large bodies?

From: Steinar Bang <sb@metis.no>
Date: 07 Feb 2001 12:14:40 +0100
To: www-lib@w3.org
Message-ID: <whelxad9sv.fsf@viffer.computas.no>
>>>>> Steinar Bang <sb@metis.no>:

>>>>> Steinar Bang <sb@metis.no>:
>>> The PUT works (to an apache with mod_put).

>>> The POST get stuck in there somewhere.

> [snip!]
>> But if so: why does this happen after successfully writing 3MB (or
>> something like that) out of 6MB?

>> And why does PUT work?  How is it different?

> From looking at HTPutAnchor() and HTPostAnchor(), the only place
> those two are different are in the call to HTRequest_setMethod(),
> and that HTPutAnchor() has a call to set_preconditions() (which is
> something to do with some caching thing I don't use... I
> think... why is there any form of caching on PUT?  I thought client
> side caching only made sense for GET?).

Or maybe the problem is on the server side?  Maybe there's some
sort of impedance mismatch between a CGI script and a servlet, and a
writing libwww client?

Maybe we end up in some sort of deadlock situation where the server
thinks it's waiting for data, while actually it has data it doesn't
read? 

"Grasping at straws"... as I said in an earlier message...:-)
Received on Wednesday, 7 February 2001 06:15:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:38 GMT