Bug #14213
RESTful UI routes should redirect to known route locations
Team Backlog:
Tom
Fixed in Releases:
Found in Releases:
Description
The title is a bit ambiguous but the idea is that we should in some cases take well known RESTful routes and have them redirect to their "true" location. For example, /products/1 is a common RESTful idiom that results in an error and could save the user some headache by redirecting them to /products/1/info instead.
Related issues
History
#1
Updated by Eric Helms about 3 years ago
Updated by - Legacy Backlogs Release (now unused) changed from 144 to 168
#2
Updated by Eric Helms about 3 years ago
- Legacy Backlogs Release (now unused) changed from 168 to 162
#3
Updated by Justin Sherrill almost 3 years ago
Updated by - Assignee set to Walden Raines
- Legacy Backlogs Release (now unused) changed from 162 to 114
#4
Updated by Walden Raines almost 3 years ago
Updated by - Status changed from New to Need more information
Are there any examples of this other than /info?
I was planning on removing /info (in favor of /products/1, for example) as part of the non-nutupane work.
#5
Updated by Walden Raines over 2 years ago
- Related to Tracker #16726: Bugs that will be fixed by removing nutupane added
#6
Updated by Walden Raines over 2 years ago
- Target version set to 155
#7
Updated by Walden Raines over 2 years ago
- Status changed from Need more information to Closed
Closing this because this issue will no longer exist when nutupane is removed.