[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: error checking out in TortoiseSVN

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Fri, 21 Jun 2013 18:37:55 +0400

On Fri, Jun 21, 2013 at 4:51 PM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> On Thu, Jun 20, 2013 at 11:23 PM, Philip Martin
> <philip.martin_at_wandisco.com> wrote:
>> Ivan Zhakov <ivan_at_visualsvn.com> writes:
>>
>>> As breser pointed on IRC all HTTP/1.1 applications MUST support
>>> chunked transfer encoding. From RFC2616:
>>> [[[
>>> All HTTP/1.1 applications MUST be able to receive and decode the
>>> "chunked" transfer-coding, and MUST ignore chunk-extension extensions
>>> they do not understand.
>>> ]]]
>>>
>>> And server is application:
>>> [[[
>>> server
>>> An application program that accepts connections in order to service
>>> requests by sending back responses.
>>> ]]]
>>
>> On the other hand the RFC also says:
>>
>> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.12
>>
>> 10.4.12 411 Length Required
>>
>> The server refuses to accept the request without a defined
>> Content-Length. The client MAY repeat the request if it adds a valid
>> Content-Length header field containing the length of the message-body in
>> the request message.
>>
>> I assume the server can send this error since it is in the RFC. The
>> client can only retry with a Content-Length request, not a chunked
>> request. So it appears that the only chunked support a server needs is
>> to be able to reply 411.
>>
> Should be fixed by r1495419 [1]:
The fix violated RFC 2145, Section 2 and reverted in r1495455:
http://svn.haxx.se/dev/archive-2013-06/0504.shtml

-- 
Ivan Zhakov
Received on 2013-06-21 16:38:48 CEST

This is an archived mail posted to the Subversion Dev mailing list.