On 14.12.2019 14:38, sebb wrote: > On Sat, 14 Dec 2019 at 13:33, Daniel Shahaf <d...@daniel.shahaf.name > <mailto:d...@daniel.shahaf.name>> wrote: > > sebb wrote on Sat, 14 Dec 2019 13:17 +00:00: > > On Sat, 14 Dec 2019 at 11:51, Daniel Shahaf > <d...@daniel.shahaf.name <mailto:d...@daniel.shahaf.name>> wrote: > > > sebb wrote on Sat, 14 Dec 2019 09:20 +00:00: > > > > The code comment here [1] and the wiki [2] both state that > section name > > > > matching is case-insensitive. > > > > > > > > However my reading of the document here [3] says this > changed in version 1.7. > > > > > > Thank you for taking the time to point out the specific text > within that > > > page you had in mind, to save us all looking for it. (It's > the first > > > "No Entry" box.) > > > > > > > These docs don't seem consistent to me. > > > > > > The two documents describe different layers. [1] and [2] > describe the > > > configuration parsing module (svn_config_*), whereas [3] — > says that > > > the implementation of authz (≤1.6) did case conversions > before or after > > > calling svn_config_*(). > > > > > > > However [2] says: > > > > [2] is not normative. The C API docs are normative. The API errata, > release notes, and CVE advisories are all fair game. But the wiki > serves > as the whiteboard in our virtual office; it isn't API documentation. > > However [1] says: > > "Section and option names are case-insensitive, but case is preserved."
Configuration files and authz files no longer use the same representation. Since you've been reading the section on config files in the wiki, I propose you also read this: https://cwiki.apache.org/confluence/display/SVN/Path-Based+Access+Control It's far from finished, but it *does* describe the differences in syntax and semantics. -- Brane
