On 08.10.14 17:30, Bernd Machenschalk wrote:
On 08.10.14 17:16, Bernd Machenschalk wrote:
Hi!
We needed to change the scheduler URL (the one in schedulers.txt). This now
appears in the correct place in the front page.
The question is how we should configure apache on the old site to force clients
to re-fetch the scheduler list from the (changed) master page.
Currently the http error at the old URL is a 404 (not found). Apparently this
doesn't help, as we don't get much traffic on the new scheduler.
FWIW a Redirect doesn't help, as the POST data gets lost.
Apparently the Client will re-fetch the scheduler list from the master URL after 10 consecutive failures to get work. If I'm not mistaken about the
backoff time scheme this could actually take several days, depending on the work cache of the Client.
An explicit permanent redirect from the web server should IMHO be a clear sign that the Client contacts an outdated URL and thus should update its
information (here re-fetch the scheduler list) _immediately_.
Could this be added to the BOINC Client, i.e. explicit Redirects be handled not as a communications error, but as a special case which triggers a new
master file fetch?
Best,
Bernd
_______________________________________________
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.
