Bug #14213
RESTful UI routes should redirect to known route locations
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Low | ||
| Assigned To: |  Walden Raines | ||
| Category: | Web UI | ||
| Target version: | Team Tom - backlog | ||
| Difficulty: | Pull request: | ||
| Bugzilla link: | Found in Katello release: | ||
| Story points | - | ||
| Velocity based estimate | - | ||
| Release | Katello Backlog | Release relationship | Auto |
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 2 years ago
- Release changed from Katello 3.0.1 to Katello 3.0.2
#2
Updated by Eric Helms about 2 years ago
- Release changed from Katello 3.0.2 to Katello 3.2.0
#3
Updated by Justin Sherrill almost 2 years ago
- Assigned To set to Walden Raines
- Release changed from Katello 3.2.0 to Katello Backlog
#4
Updated by Walden Raines almost 2 years ago
- 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 1 year ago
- Related to Tracker #16726: Bugs that will be fixed by removing nutupane added
#6
Updated by Walden Raines over 1 year ago
- Target version set to Team Tom - backlog
#7
Updated by Walden Raines over 1 year ago
- Status changed from Need more information to Closed
Closing this because this issue will no longer exist when nutupane is removed.