subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Foad <>
Subject Re: svn commit: r1715269 - /subversion/branches/1.9.x/STATUS
Date Fri, 20 Nov 2015 15:26:38 GMT
Bert Huijben wrote:
> There is currently no way how a user with released software can encounter
> this problem.

Thank you for sharing this useful background information about this
change. I think it would be better if you put that information in the
STATUS file, because anyone evaluating the backport proposal should be
aware of the reasons for this change (of course they should be reading
dev@ too) and also I think it will be easier to find this information
in the future if you attach it directly to the backport proposal, or
alternatively to the commit log messages. That was my point.

- Julian

> BTW I think I have a solution for the replay problem at the cost of a few lb
> of ram.

Julian Foad wrote:
> Bert Huijben wrote:
>>> Subject: svn commit: r1715269 - /subversion/branches/1.9.x/STATUS
>>> + * r1715224, r1715232, r1715262
>>> +   ra_serf: Fix setting Content-Type header in 3 outgoing xml requests
>>> +   Justification:
>>> +     We should properly implement our wire protocol.
>>> +   Votes:
>>> +     +1: rhuijben
>> These were found via a bug in httpd 2.4.17, where it doesn't handle
>> requests via http/2 with a body unless Content-Length or Content-Type is
>> set.
>> This should not affect normal Subversion usage, but it makes our http
>> usage a bit cleaner.
> It would be a good idea to copy this information into the STATUS file.
> - Julian

View raw message