Skip to content
This repository has been archived by the owner on Mar 28, 2019. It is now read-only.

Handle 503 — when the database fail, we should log the error and return a 503 #21

Closed
Natim opened this issue Feb 24, 2015 · 2 comments · Fixed by #77
Closed

Handle 503 — when the database fail, we should log the error and return a 503 #21

Natim opened this issue Feb 24, 2015 · 2 comments · Fixed by #77
Assignees

Comments

@Natim
Copy link
Contributor

Natim commented Feb 24, 2015

Today it is a 500

@Natim
Copy link
Contributor Author

Natim commented Feb 24, 2015

Same thing for session's backends.

@Natim
Copy link
Contributor Author

Natim commented Mar 2, 2015

We should add a raise BackendError in our backends and catch BackendErrors when calling the backend from views.

@leplatrem leplatrem self-assigned this Mar 10, 2015
@Natim Natim closed this as completed in #77 Mar 11, 2015
@Natim Natim removed the doing label Mar 11, 2015
Natim added a commit that referenced this issue Mar 11, 2015
…for_503

Handle backend errors for 503 (fixes #21)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants