On 09.01.2015 10:46, pierre.vi...@postfinance.ch wrote:
>
>> -Ursprüngliche Nachricht-
>> Von: Philip Martin [mailto:philip.mar...@wandisco.com]
>> Gesendet: Mittwoch, 7. Januar 2015 14:51
>> An: Viret Pierre, PF54
>> Cc: users@subversion.apache.org
>> Betreff: Re: AW: AW: Segmentation Faul
Philip Martin writes:
> I can't reproduce this against a standard server.
I think I have worked it out. There was an error in my script: one of
the XML response lines was missing a '\n' and this originally caused the
client to report the HTTP response as too short, so I "fixed" it by
added a tr
Philip Martin writes:
> I've converted your trace into a Python script to implement a server
> that behaves like yours.
I may have reproduced the problem. If I remove the 'Connection: close'
headers and continue to force v1 I can get the client to crash using the
dummy server. I suppose that m
writes:
> The status line is not blocked. The debugging message means that we
> have got an header with a null key and with the status line as value:
> in this case the header is not added to the request sent back to the
> client. This seems to be common that some HTTP Implementations return
> su
