sorry for beeing unclear before. i did want to write that the standard
should include a unique method of retrieving versions, and not leave
it to the server. and i'm still wondering what drawbacks this could
have - personally i do not see any for such a simple and natural
problem. for me its something like "leave the url syntax to be defined
by the server" for http servers.
-solo.
On 8/22/05, Phillip Susi <psusi@cfl.rr.com> wrote:
> I find that you can access older revisions via web browser by using URLs
> like this:
>
> https://server/svn/!svn/bc/123 where 123 is the revision number you seek.
>
> I'm not sure why this isn't documented in the SVN book. According to
> the DelvtaV standard, the URL syntax used to differentiate between
> versions is left up to the server, and the client needs to use special
> requests to ask the server what URL to use to access specific versions.
> I looked at apache's access log though and found that svn was using
> URLs like the above, and gave it a try and it worked.
>
>
>
> Michael Sinz wrote:
> > solo turn wrote:
> >
> >>hi,
> >>
> >>why is it not possible to extend webdav or deltav standard to also
> >>have a means of retrieving a version/revision of a resource like:
> >>http://svn.collab.net/repos/svn/trunk/README?rev=1000
> >>which would allow normal apache access control on the url?
> >
> >
> > Actually, using the rewrite trick that I have in the Insurrection tools,
> > this sort of works. That is, the mod_authz_svn does all of the URL
> > access controls because the access controls are handled before the
> > .htaccess rewrite rules run.
> >
> >
> >>is there any disadvantage in this approach i am not able to see?
> >
> >
> > Other than making mod_dav_svn be more than what it is (and it already
> > is a relatively large bit of code)
> >
> > There are other ways to get the same results since the rewrite rules for
> > a directory apply after mod_authz_svn accepted the requested path.
> > (If mod_authz_svn rejected the path, the rewrite engine never even gets
> > a chance to run)
> >
> > For example, here is the .htaccess I use and one previous version:
> > (note - in my setup, this goes into the "/" directory of the web server)
> >
> > http://svn.sinz.com/svn/Insurrection/trunk/.htaccess?Insurrection=get&r=221
> > http://svn.sinz.com/svn/Insurrection/trunk/.htaccess?Insurrection=get&r=220
> >
> > Now, this is a repository that requires user authentication for read access:
> >
> > http://svn.sinz.com/svn/example2/trunk/fold/fold.html?Insurrection=get&r=6
> >
> > (Sorry, no public user name defined, but this is mod_authz_svn doing the
> > authentication, just like it does for the SVN access rights)
> >
> > Note that there is no way to secure a revision number itself. So if you have
> > access to the file, you have access to its history.
> >
> > The reason for the get operation is that I also use this to provide access
> > controls on the log files, diffs, etc., that Insurrection provides the web
> > interface for. It makes for a really nice interface to let mod_authz_svn
> > do all of the authentication.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 23 11:25:18 2005