It is possible to have native HTTP redirects for pages moved or renames in Confluence?
One condition: this has to work by default, without having to ask the user to do somethign else after he moves or renames the page.
I was amazes to discored that this basic functionality was not a core feature by design.
According to the docs, all links should update automatically when you move or rename a page. You just have to make sure your links are not web-links that start with http...use Confluence page links instead.
Maybe we're not thinking of the same thing.
Shortly, Confluence should be able to detect 301 and 308 HTTP responses and correct the links inside the pages. Also, Confluence shold return 301 HTTP responses for pages that were moved or renamed. These are two different features but that by combining do solve the missing page problem in the correct way (the web way). The current behavioud of responding with 200 response and a page that is telling you that the content was moved is silly and denotes a clear lack of knowledge on how an web application is supposed to be implemented.
Ironically, clicking that very link posted earlier (https://confluence.atlassian.com/display/DOC/Moving+a+Page) now renders as a 404 because someone moved the page:
Documentation in most organisations will exist in a continuous state of flux, and probably as a heterogeneous combination of emails / multiple wikis / documents on fileshares / links embedded in source code/comments / etc. etc... most of which will likely have static links, and these will grow increasingly stale as time passes. Having them return 404 for a moved Confluence resource harms the user-experience, and therefore (likely) also the adoption of Confluence. It's also contrary to RFC7231:
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG