On Tue, Sep 20, 2016 at 4:59 AM, Zdenek Sedlak <d...@apgrco.com> wrote:
> On 2016-09-17 09:49, Daniel Shahaf wrote:
> Branko Čibej wrote on Sat, Sep 17, 2016 at 03:29:25 +0200:
> But be aware that if the RHEL 7 version of httpd is *not* patched, your
> SVN server will be broken in subtle ways.
> I really have no idea how to check that.
> I believe the relevant change is this:
> *) mod_dav: dav_resource->uri is treated as unencoded. This was an
> unnecessary ABI changed introduced in 2.4.6. PR 55397.
> I opened a support case @ Red Hat. Hopefully Red Hat will be willing to
> back-port this change back to 2.4.6, as this may affect more product relying
> on DAV.
You can also dump the whole problem and switch to svn+ssh based
access. I've been a firm supporter of that for years. The default
behavor of the HTTP clients to store passwords in plain text in
$HOME/.subversion/ has been one of my big reasons to recommend against
HTTPS access. And avoiding the possible detrimental behavior of HTTP
or HTTPS proxies is also helpful. There's nothing like being in a
hotel room that says "free wifi!!" and finding out that you have to
register on the local wifi before you can use it, and it *keeps timing
out and forcing a re-registration" right in the midst of publishing