Skip to content

Standardize Error Responses #897

Open
mikldt opened this Issue Mar 2, 2014 · 0 comments

3 participants

@mikldt
Concerto Digital Signage member
mikldt commented Mar 2, 2014

At the current moment, 404 and 500 errors are served from static, non-template pages in /public.

Error pages should appear to be "in-app". Further, they need to be consistent across the application. An important part of this effort is code review to make sure that errors are handled in an efficient and non-circuitous fashion.

I'm outlining some goals here:
https://github.com/concerto/concerto/wiki/Error-handling

@mikldt mikldt self-assigned this Mar 2, 2014
@mikldt mikldt added a commit that referenced this issue Mar 3, 2014
@mikldt mikldt Route all exception handling* to ErrorsController
Progress on #897
* Excludes Authorization issues, for now.
ee2b463
@augustf augustf added this to the 0.9.0 KiloBalrog milestone Mar 6, 2014
@bamnet bamnet removed this from the 0.9.0 KiloBalrog milestone Mar 6, 2014
@augustf augustf added this to the 0.9.1 milestone Apr 4, 2014
@augustf augustf modified the milestone: Concerto 2.3 (Frontend) Nov 26, 2014
@augustf augustf modified the milestone: Concerto 2.3 (Frontend) Aug 21, 2015
@augustf augustf modified the milestone: 2.31 Sep 13, 2015
@augustf augustf modified the milestone: 2.3.2 Dec 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.