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 10:43:48 +0100
To: www-lib@w3.org
Message-ID: <wh3ddqeskr.fsf@viffer.computas.no>
>>>>> Steinar Bang <sb@metis.no>:

>> The PUT works (to an apache with mod_put).

>> The POST get stuck in there somewhere.

> This is where it's stuck:
> ...
> Alert Call.. No entry found for opcode 16
> Write Socket WOULD BLOCK 6 (offset 2919488)
> Uploading... Callback returned 200
> LibwwwNotify::writedata(1)  socket: 6
> Host Event.. WRITE passed to `http://localhost/metis/repository'
> Buffer...... Flushing 0x83c8f20
> Write Socket 65824 bytes written to 6
> Alert Call.. No entry found for opcode 16
> Write Socket 61952 bytes written to 6
> Alert Call.. No entry found for opcode 16
> Write Socket WOULD BLOCK 6 (offset 3047264)

[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?).
Received on Wednesday, 7 February 2001 04:44:09 GMT

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