Thanks a lot!
I have to admit that I indeed did miss the "Permanent" flag.
A "RedirectPermanent" seems to work!
However this leaves the scheduler URL in the client at the old URL, i.e. the client doesn't really take notice, just the underlying curl(?). I vaguely
remember that the master file will be re-fetched periodically in any case? Is this so, and if so, what period? 1 week?
Best,
Bernd
On 09.10.14 11:59, Tomi Juhani Asp wrote:
Hi!
Not sure if this will solve your issue but we were struggling a bit with
redirects as well but solved it by giving the rewrite rule a [R=301] flag. 301
code means that the resource has been moved permanently and all the following
requests should be made to the new address. By default, if using just R flag,
apache issues different status code.
Cheers,
Tomi
________________________________________
From: boinc_projects [[email protected]] on behalf of
Bernd Machenschalk [[email protected]]
Sent: 09 October 2014 11:38
To: BOINC Developers Mailing List
Cc: Boinc Projects
Subject: Re: [boinc_projects] [boinc_dev] change scheduler URL
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_projects mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
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.
