Bug 1041962

Summary: [RFE][keystone]: Keystone should respond to Web Browser with HTML
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/keystone/+spec/render-html
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:25:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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