https://bugzilla.redhat.com/show_bug.cgi?id=1490994
--- Comment #6 from Karsten Wade <kw...@redhat.com> --- (In reply to Amye Scavarda from comment #5) > http://www.gluster.org/git-reincarnating-remote-master-branch-so-you-can- > easily-pr-to-upstream/ is the answer to the direct one. > Unfortunately, it looks like the import done by the web developers has > stripped out all of the previous URL date information. > > What's the best way forward here? Couple of thoughts come to mind, which are a bit brute-force. I think then we'd have to have an X:Y mapping of every single source and destination as explicit full paths mapped to full paths. How many posts are there? We'd need a rewrite rule for each one. Can the HTTP server handle N 100s of these rewrites? Should seem so, yes? (It occurs to me that if you did want the full dates in the path again, we could go re-import of data. Then have a set of rewrite rules from the source stripped-of-dates-path to the new path -- rewrite rules coming AND going. Idea is to gracefully transition from the old and an interim-new to a permanent new.) If we did all the above with 301 codes, could we get the search indexing resolved too? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=pgGYuO5rpV&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra