Implement Better HTTP Usage Through-out Horizon (Status Codes, Content-Type Headers, Accept Headers, etc...)
Registered by
John Postlethwait
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.
Blueprint information
- Status:
- Complete
- Approver:
- Gabriel Hurley
- Priority:
- Low
- Drafter:
- John Postlethwait
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Deferred
- Milestone target:
- None
- Started by
- Completed by
- Matthias Runge
Related branches
Related bugs
Sprints
Whiteboard
this is superseeded by the several angular blueprints
(?)