On 1/29/15 4:40 AM, Brendon Abbott wrote: > Since writing this original email, I have found that the difference between > the > working instance and the non-working instance is not the repository, but the > client. 1.6.17 works fine, whilst 1.8.11 does not.
This issue sounds suspiciously like what's described here to me (note the second warning box): http://subversion.apache.org/docs/release-notes/1.8.html#mod_dav_svn-fsmap I'd check to see if your server has been misconfigured to modify the file contents being sent to the client. The reason you're seeing a difference in behavior with older clients is likely because the default of using skelta style updates is now the default. When an update happens via bulk update mode the file content is included in the report and the filter that is triggering with a direct request of the content does not get triggered. The behavior change here is covered in this bit of the release notes as well: http://subversion.apache.org/docs/release-notes/1.8.html#serf-skelta-default
