Thomas Bellembois wrote:
I rely on the "contentLength" parameter of the HTTP request.
To update quota MD when the request is done I use the resource MD
(DAV:getcontentlength).
I have made tests using many DAV clients and for one of them (based on
the Slide client library) I could exceed quotas with a put method.
Bad luck :-( I thought I had finished...
I have discovered that the HTTP contentLength parameter was -1 for this
request.
According to the HTTP/1.1 standard �14.13
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.13
the Content-Length header SHOULD be specified by each client.
(Ie, it is not a MUST in the standard.)
I suppose that you are seeing a multipart/byteranges encoded message
or Transfer-Encoding: chunked as defined in HTTP/1.1.
See the spec �4.4 for some hints about determining message lengths in
these cases:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4
More info on HTTP/1.1 chunked transfer-encoding is available here:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1
Hopefully, you will be able to read up on the HTTP spec and find out
how the Slide HTTP-server deals with the different transfer encodings
etc and find which Slide-internal method you can call to reliably
find out the message length.
HTH,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
