On Tue, Jan 5, 2010 at 11:28, Kylo Ginsberg <k...@kylo.net> wrote: > So one bug/enhancement here is to improve client reporting when it > encounters a 207. > > But back to the root of my original problem: I can create a "svn:" > property via the svn access method without any errors which then > results in errors when accessed via the http access method. That > seems like a bug, yes? But is the problem that the svn access method > *allows* this bogus property, or that http chokes on it?
Flip a coin. One could make either argument about the root of the problem. The bigger question is, if you code to prevent the bogus property from being set, what will happen when you access a repository via HTTP which already had those bogus properties set? You've stopped people from setting them in the future, which is fine - but you still have to handle the scenario where someone accesses the ones that were previously set.
