Re: Rejecting commits to a 1.5 server from clients < 1.5

Justin Erenkrantz wrote:
> On Oct 23, 2007 1:21 PM, Blair Zajac <blair@orcaware.com> wrote:
>> I'm not looking for a 100% reliability. As long as somebody downloads a well
>> known binary, say Subclipse, our .exe's or TortoiseSVN who will do a good build,
>> or downloads and compiles from source and doesn't modify the source, that's good
>> enough for me.
>
> For WebDAV installs, you can do a BrowserMatch to reject non 1.5 user
> agent strings. Both ra_dav and ra_neon include the SVN/<version
> number> in the User-Agent headers. This is the simplest and
> most-straightforward way to block WebDAV accesses.
>
> So, really, you only need to do something for ra_svn... -- justin

If I may request one tiny additional feature for the agent strings:
currently, the agent string is a fixed #define deep inside the svn
library. I'd like to customize that one to include some client specific
stuff. Something like

#ifdef CUSTOM_CLIENT_AGENT_STRING
#define SVN_FULL_AGENT_STRING CUSTOM_CLIENT_AGENT_STRING + SVN_AGENT_STRING
#else
#define SVN_FULL_AGENT_STRING SVN_AGENT_STRING
#endif

that way, svn clients can add their own string, and hosters could create
some statistics about the use of svn clients. Kind of like the browser
statistics for websites.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org