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

500/503 HttpException subclasses #103

Merged

Conversation

danielfinke
Copy link
Member

No description provided.

@k-anderson
Copy link
Contributor

@danielfinke which APIs return a 500 not_found? I suspect those are bugs :)

@danielfinke
Copy link
Member Author

@k-anderson it looks like the only API to behave that way was GET to phone_numbers when the number didn't exist. I compared the response from our 3.22 cluster and our 4.1 cluster. The issue must have been patched at some point. 3.22 gives a 500 not_found, 4.1 as expected returns a 404.

I guess the decision here is whether to bother supporting the 3.22 response. If not, let me know, I'll remove that part of the PR.

@swysor
Copy link
Contributor

swysor commented Feb 1, 2018

We don't care about the 3.22 compatibility so you can remove that part from this PR and I will merge this. Also note, I merged the patch change PR and made a tag 2.0.1 which includes this non-backwards compatible change.

@danielfinke danielfinke force-pushed the master-pr-500-503-http-exception-subclasses branch from 71965e6 to 926dd9c Compare February 1, 2018 00:27
@danielfinke
Copy link
Member Author

@swysor Alright, I have removed the 3.22 compatibility code. Thanks for tackling these PRs!

@swysor
Copy link
Contributor

swysor commented Feb 1, 2018

Thanks for all the great contributions. Keep em coming!

@swysor swysor merged commit a916dbf into 2600hz:master Feb 1, 2018
@danielfinke danielfinke deleted the master-pr-500-503-http-exception-subclasses branch February 1, 2018 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants