Answer

[git.ikiwiki.info.git] / doc / todo / aggregate_401_handling.mdwn

diff --git a/doc/todo/aggregate_401_handling.mdwn b/doc/todo/aggregate_401_handling.mdwn
index cc65ad00efcdb79fb14e8b23d870f4b8e1c66e8e..125e74e7659e01e1d39c0d58d07a89f4772ee676 100644 (file)
--- a/doc/todo/aggregate_401_handling.mdwn
+++ b/doc/todo/aggregate_401_handling.mdwn
@@ -1,11 +1,11 @@
-The aggregate plugin's handling of http 401 (moved permanently) could be
-improved. Per [[rfc 1945]]:
+The aggregate plugin's handling of http 301 (moved permanently) could be
+improved. Per [[!rfc 1945]]:
 
 > The requested resource has been assigned a new permanent URL
 > and any future references to this resource should be done
 > using that URL.
 
-So ideally aggregate would notice the 401 and use the new url henceforth.
+So ideally aggregate would notice the 301 and use the new url henceforth.
 
 It's a little tricky because the aggregate plugin can't just edit the page and
 change the url in the preprocessor directive. (Because committing such an
@@ -14,3 +14,7 @@ url for the site, which may also have changed. Perhaps the thing to do is
 record the new url in the aggregate plugin's state file, and change the message
 to "Processed ok (new url http://..)", and let the user deal with updating
 the page later.
+
+----
+
+Assuming they really mean **301** (because 401 is "Unauthorized"), I've updated the body of the text but the page itself should really be renamed. -- adam.
\ No newline at end of file