On Mon, Aug 14, 2006 at 07:16:28PM +0200, Steve Bennett wrote:
On 8/14/06, Timwi timwi@gmx.net wrote:
a) It hard redirects you, and there's absolutely no link back to where you came from. Very bad for maintenance, working on the redirect itself etc. b) It redirects you, but leaves the link back to the original redirecting page.
or (c) It hard redirects you, and there's a link back to where you came from.
Ok, what do "hard direct" and "soft redirect" mean in this context exactly? Let's take some page A which redirects to page B. They're hosted directly at wiki.org.
Currently wiki.org/A shows the content of wiki.org/B, but with a link back to A. The URL shows wiki.org/A.
You're proposing that wiki.org/A force a (server-side?) redirect to wiki.org/B, display the content of B, with a link back to A, and yet the URL shows wiki.org/B? The question is, how does MediaWiki know to show the link back if the URL is only wiki.org/B, and not wiki.org/B&red=A or something?
The problem is that we want a "clean" URL when we land, and yet we also want a backlink on the page proper. There doesn't seem to be any good way to get both.
I, too, think it would be nice to make it as difficult as possible to bookmark a URL that's the *source* of a redirect (which I presume is what everyone's on about), but as brion says, there doesn't seem to be any clean way to do that and still have link back to the redirect -- without maintaining state in the server, which is entirely uncalled for here.
IMHO.
Timwi clearly thinks that one of our premises, or our conclusion, are incorrect, but doesn't seem to have provided details yet.
Cheers, -- jra