Page MenuHomePhabricator

When users visit a Phame post URI with an old blog ID, canonicalize the URI instead of 404'ing
ClosedPublic

Authored by epriestley on Jul 31 2019, 6:40 PM.
Tags
None
Referenced Files
F18780596: D20688.id.diff
Sun, Oct 12, 5:44 PM
F18756392: D20688.id.diff
Sun, Oct 5, 11:19 AM
F18753908: D20688.diff
Sat, Oct 4, 8:45 PM
F18679665: D20688.id49341.diff
Sep 26 2025, 1:10 AM
F18641838: D20688.diff
Sep 18 2025, 9:58 PM
F18608475: D20688.id49342.diff
Sep 14 2025, 1:15 AM
F18567203: D20688.id.diff
Sep 9 2025, 3:35 PM
F18519254: D20688.diff
Sep 5 2025, 4:26 PM
Subscribers
None
Tokens
"Orange Medal" token, awarded by Krinkle.

Details

Summary

Fixes T13353. If you:

  • Visit a blog post and save the URI.
  • Move the blog post to a different blog.
  • Revisit the old URI.

...we currently 404. We know what you're trying to do and should just redirect you to the new URI instead. We already do this if you visit a URI with a noncanonical slug.

Test Plan
  • Created post A.
  • Copied the live URI.
  • Moved it to a different blog.
  • Visited the saved URI from the earlier step.
  • Before: 404.
  • After: Redirect to the canonical URI.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable