Bug 1042041

Summary: [RFE][horizon]: Implement Better HTTP Usage Through-out Horizon (Status Codes, Content-Type Headers, Accept Headers, etc...)
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/horizon/+spec/global-ajax-communication
Whiteboard: upstream_milestone_none upstream_status_deferred upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:24:49 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:42:10 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/global-ajax-communication.

Description:

We need to figure out, in a holistic manner, how, site-wide we would like to handle AJAX communication over HTTP.

We should stick to HTTP status codes and the standards for their use/meaning in responses.

We should use Content-Type back and forth to communicate what is being transferred in either direction.

We should use the Accept header on the back-end to determine HOW to render a response to specific requests. 

This would mean that if someone wants to add support for XML, no new endpoints should need to be written in order to render a given URI in XML, one would just be able to set the request Accept header, and create a response formatter for that Accept format.

Specification URL (additional information):

None