Bug 1041962 - [RFE][keystone]: Keystone should respond to Web Browser with HTML
Summary: [RFE][keystone]: Keystone should respond to Web Browser with HTML
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:19 UTC by RHOS Integration
Modified: 2015-07-22 17:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:25:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 20:19:04 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/render-html.

Description:

When pointing a browser at Keystone, it currently displays XML.  If the browser will accept HTML, Keystone should respond with HTML

While a complete user experience is beyond the scope of the core keystone project, it should be easy for deployments to customize base on the concept of progressive enhancement:

Visiting a page should perform a transform from Python to HTML code much like what is done via JSON.  The nesting/hierarchy will use DL/DT/DD tags for key-value pairs and UL for arrays.

Links will be specially handled to be proper hyperlinks.

This blueprint only handles the original display of existing pages, not additional navigation nor form generation.


Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.