1 The aggregate plugin's handling of http 401 (moved permanently) could be
2 improved. Per [[rfc 1945]]:
4 > The requested resource has been assigned a new permanent URL
5 > and any future references to this resource should be done
8 So ideally aggregate would notice the 401 and use the new url henceforth.
10 It's a little tricky because the aggregate plugin can't just edit the page and
11 change the url in the preprocessor directive. (Because committing such an
12 edit would be .. hard.) Also, aggregate directives may also include a separate
13 url for the site, which may also have changed. Perhaps the thing to do is
14 record the new url in the aggregate plugin's state file, and change the message
15 to "Processed ok (new url http://..)", and let the user deal with updating