When a content source used by a feature returns a redirect response from the Content API, instead of throwing an exception and failing, follow the redirect!
Scenario: The homepage editor uses a feature on a Page to call in a particular story by entering a canonical URL. Then someone else goes and changes the canonical URL of that story, which inserts a redirect for the old URL (which is not supposed to happen much but it does happen - even in Ellipsis this is supported). The feature calling for the old URL now breaks due to the exception and the homepage editor or whoever is not going to get any warning that this has happened other than the feature breaking.
Having to go back and manually update the feature with the updated canonical when the API is already saying “hey that thing you want is over there” feels like we got 3/4 of the way to not needing human intervention at all.
Alasdair McKie
| Categories | Content Services |
| I need it... | Month |
We're planning for some future content search capabilities that will allow for content to be discoverable by ID. We think that this might address the redirect issue because the content ID won't change.