Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
From: Bob Archer <Bob.Archer@amsi.com>
To: Chris Evans <chris.evans@gresearch.co.uk>, "users@subversion.apache.org"
	<users@subversion.apache.org>
Date: Tue, 7 Feb 2012 14:05:55 -0500
Subject: RE: Restricting access to old revisions of a project?
Thread-Topic: Restricting access to old revisions of a project?
Thread-Index: AczibVgFYMBCyRK/RM6KGQXs81vnUgDXgZoQ
Message-ID: <CB4587DA62024B40B9F929ECF639210F32C3AD21F0@USALWEXMB4.infor.com>
References: <35D3879452B3044DA3CA8685455C9174077B49D207@rbpexch1.uberit.net>
In-Reply-To: <35D3879452B3044DA3CA8685455C9174077B49D207@rbpexch1.uberit.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> I've had a request to restrict access to revisions of certain SVN project=
s in a
> repository older than a set revision number. My repo is accessed via Apac=
he
> HTTPS. Has anybody had any experience of this or would know where to star=
t?
> I'm guessing it could be possible in the httpd config to deny access if t=
he http
> request contains the revision, but I'm not sure what modules or config wo=
uld
> allow this. Any help would be greatly appreciated.

Copy at the lowest revision to a new path and restrict users to that path. =
Of course, this doesn't help if you are beyond that rev.

It may be something you can do with a hook script. Not sure.

BOb