Re: E120105 (or not): The server sent an improper HTTP response

Hi Diego,

I can provide you with some clues about this (this is a wild guess
since I known nothing about your environment except the fact that you
run Subversion server on Raspberry Pi device with Ubuntu):

1. If you get this error with Subversion 1.8 client, try Subversion
1.7 client. If SVN 1.7 works without any errors, configure this
directive in your httpd.conf, restart Apache and see if you can still
reproduce the error:
[[
SVNAllowBulkUpdates Prefer
]]

Should look like this:
[[
<Location /svn/>
    SVNAllowBulkUpdates Prefer
</Location>
]]

2. Disable antivirus on the client machine and attempt reproducing the
error. You might be required to temporarily remove the antivirus
because it can still work even when disabled. What antivirus do you
use BTW?

On Wed, Apr 22, 2015 at 8:44 PM, Diego Sucaria
<lordblack.diego_at_gmail.com> wrote:
> Hello!
>
> I'm having the same problem on Ubuntu, installed on the Raspberry pi2.
>
> svn: E120105: ra_serf: The server sent an improper HTTP response
>
> searched everywhere and I can't find a solution.
>
> Did you fixed it?
>
>
> On Friday, June 6, 2014 at 3:15:49 PM UTC-3, John Adams wrote:
>>
>> Hi, folks,
>>
>> I'm one of our two subversion administrators and I've got a problem
>> that puzzles all of us. Most of our users are reporting an issue doing
>> checkins, being able to commit one file at a time, then getting the message
>> "Error running context: The server sent an improper HTTP response",
>> sometimes prepended with the code E120105. This is happening using:
>>
>> Windows, both via the client and the command line: TortoiseSVN 1.8.6,
>> Build 25419 - 64 Bit , 2014/04/12 11:40:48
>> Mac OS X on the command line: svn, version 1.8.8 (r1568071) compiled
>> Apr 22 2014, 22:31:17 on x86_64-apple-darwin13.1.0
>>
>> but not:
>>
>> Linux using svn, version 1.6.11 (r934486) compiled Apr 3 2013,
>> 04:40:28
>>
>> The server is running subversion 1.8.0 and Apache/2.2.15.
>>
>> I've read about the neon/serf libraries and figure the neon libraries
>> on our Linux server are old enough not to have the issue and our serf
>> libraries aren't new enough to have it fixed, but I'm just guessing. My
>> plan, unless you have a better one, is to upgrade as soon as possibe to
>> 1.8.8 or 1.8.9. Can you help?
>>
>> Thanks,
>>
>> John A

--
With best regards,
Pavel Lyalyakin
VisualSVN Team