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

3xx status codes should mean success #78

Merged
merged 1 commit into from
Dec 7, 2015
Merged

3xx status codes should mean success #78

merged 1 commit into from
Dec 7, 2015

Conversation

jolynch
Copy link
Collaborator

@jolynch jolynch commented Dec 4, 2015

Previously nerve considered 3xx to be failure, which is inconsistent
with most other healthcheck systems (e.g. haproxy or nginx).

Should fix #77

Previously nerve considered 3xx to be failure, which is inconsistent
with most other healthcheck systems (e.g. haproxy or nginx).

Should fix #77
@jolynch
Copy link
Collaborator Author

jolynch commented Dec 7, 2015

@igor47, @rickypai Do you guys have any opinions on this. If not I'm going to ship it.

@evie404
Copy link
Collaborator

evie404 commented Dec 7, 2015

seems ok to me. update the test to include a 3xx case?

@jolynch
Copy link
Collaborator Author

jolynch commented Dec 7, 2015

@rickypai I don't believe there are any tests really ... which test are you thinking?

@jolynch
Copy link
Collaborator Author

jolynch commented Dec 7, 2015

I'm going to merge and follow up with a test when there are tests.

jolynch added a commit that referenced this pull request Dec 7, 2015
3xx status codes should mean success
@jolynch jolynch merged commit 01bcc63 into master Dec 7, 2015
@panchr panchr deleted the jlynch_3xx_is_ok branch March 19, 2020 20:03
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.

Should nerve consider a 3xx status to be successful?
2 participants