I changed the master URL of my project in the past, from my experience I can tell you that it won't cause too much troubles if you leave the old URL working for some time.
In my case, I set up the old domain name as an alias (CNAME) for the new one, and I used apache's mod_rewrite combined with mod_proxy to transparently redirect requests from the old domain/path to the new one (probably not required if only the domain is changed). At first I tried simple http redirect (status 301, tried also 302, 303 and 307); for a large number of clients it caused problems reaching the file upload handler and the scheduler. /TJM On Mon, 12 Oct 2009 00:29:42 -0300 Nicolás Alvarez <[email protected]> wrote: >El Lunes 12 Oct 2009 00:16:39 Mark Pottorff escribió: >> So... what about all those volunteers attached to the >>old project URL? With >> results, from the old URL, ready to be returned to the >>project? They will >> be trying to hit the old upload server, and scheduler. > >That depends on whether the old URL stops working or not. >It may be configured >to redirect to the new one, in which case clients will be >able to keep >reporting work. Adding such redirection was out of the >scope of my >instructions; but feel free to add it yourself :) > >-- >Nicolas >_______________________________________________ >boinc_dev mailing list >[email protected] >http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >To unsubscribe, visit the above URL and >(near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
