[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion clients following HTTP 302 response codes.

From: Branko ─îibej <brane_at_apache.org>
Date: Sun, 15 Apr 2018 19:41:52 +0200

On 15.04.2018 15:20, Paul Hammant wrote:
> The main conversation - PROPFIND, OPTIONS etc with a canonical
> centralized server, _but_ select GETs (among many) being redirected to
> other URLs.
> My testing didn't show that that was supported. As a good XPer, I
> should be able to conjure up a script to show that but I can't, so I
> mean manual testing for now.

That's true, redirects are followed only during RA session creation, so
that's during the initial handshake with the server. All requests within
the session then use the resolved URL and expect the repository not to
move elsewhere.

I'm still wondering what you're aiming for though. An obvious example
would be offloading resource content storage from the repository server
to some other storage. But if you want to do that, relying on redirects
is hardly a good option, since you'd be increasing the number of
requests and hence the latency. Transparent load balancing on the server
side is probably a much better solution.

Other than that consideration, I don't see any technical barrier to
supporting redirects within a live session ... the DAV/HTTPv2 experts
should chime in here.

-- Brane
Received on 2018-04-15 19:41:58 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.