Project

General

Profile

Actions

Bug #14213

closed

RESTful UI routes should redirect to known route locations

Added by Eric Helms about 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Web UI
Target version:
Difficulty:
Triaged:
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 1 (0 open1 closed)

Related to Katello - Tracker #16726: Bugs that will be fixed by removing nutupaneClosedWalden Raines09/28/2016

Actions
Actions #1

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release changed from 144 to 168
Actions #2

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release changed from 168 to 162
Actions #3

Updated by Justin Sherrill over 7 years ago

  • Assignee set to Walden Raines
  • translation missing: en.field_release changed from 162 to 114
Actions #4

Updated by Walden Raines over 7 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.

Actions #5

Updated by Walden Raines over 7 years ago

  • Related to Tracker #16726: Bugs that will be fixed by removing nutupane added
Actions #6

Updated by Walden Raines about 7 years ago

  • Target version set to 155
Actions #7

Updated by Walden Raines about 7 years ago

  • Status changed from Need more information to Closed

Closing this because this issue will no longer exist when nutupane is removed.

Actions

Also available in: Atom PDF