Bug 1042041 - [RFE][horizon]: Implement Better HTTP Usage Through-out Horizon (Status Codes, Content-Type Headers, Accept Headers, etc...)
Summary: [RFE][horizon]: Implement Better HTTP Usage Through-out Horizon (Status Codes...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/hori...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:42 UTC by RHOS Integration
Modified: 2015-03-19 17:24 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

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


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