https://issues.apache.org/bugzilla/show_bug.cgi?id=35077
--- Comment #8 from Timur I. Bakeyev <[email protected]> 2010-12-28 10:19:23 EST --- (In reply to comment #7) > Trying to guess where the repository part should start will lead to > ambiguities > with more complex regular expression. I think the only general solution is to > add a DAVBaseURL directive which allows the user to specify what he actually > meant. I don't see, how it is related. There is nothing to do with the repository path in that particular case. We have a combination of LocationMatch, mod_dav and mod_dav_svn. The first one is responsible to match the location, which was requested from the server with the given configuration block. And the result of it is binary - either 'yes' or 'no'. and if it is 'yes' - we have very exact path(local part of the URI) that did match it! If it matched something, that wasn't aimed to - well, blame the writer of the regex. But, in any case, as soon as the block matched - we should have exact URI which should be passed to the mod_dav instead of cryptic regular expression. I'm not sure how easy is to implement it, but at least, that what I'd expect, comparing with the behavior in case of Location. There is absolutely nothing that makes this situation specific to the mod_dav_svn. It just consumes what mod_dav passed to it, and in this situation mod_dav passes garbage. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
