Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Returning JSON responses for common upstream server errors #970

Merged
merged 1 commit into from
Feb 10, 2016

Conversation

subnetmarco
Copy link
Member

Closes #927.

@subnetmarco subnetmarco self-assigned this Feb 9, 2016
@subnetmarco subnetmarco force-pushed the fix/json-error-responses branch 4 times, most recently from 7144fb3 to 1bdd099 Compare February 9, 2016 03:19
@subnetmarco subnetmarco force-pushed the fix/json-error-responses branch from 1bdd099 to 676d2ce Compare February 9, 2016 03:25
@subnetmarco subnetmarco added pr/status/needs review pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release) and removed pr/status/needs review labels Feb 9, 2016
subnetmarco added a commit that referenced this pull request Feb 10, 2016
Returning JSON responses for common upstream server errors
@subnetmarco subnetmarco merged commit 25edc4e into next Feb 10, 2016
@subnetmarco subnetmarco deleted the fix/json-error-responses branch February 10, 2016 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant