Skip to content
This repository has been archived by the owner on Dec 20, 2024. It is now read-only.

Accept all 2xx and 3xx HTTP status codes as successful #228

Merged
merged 2 commits into from
May 22, 2014
Merged

Accept all 2xx and 3xx HTTP status codes as successful #228

merged 2 commits into from
May 22, 2014

Conversation

davidrautert
Copy link
Contributor

Currently the only 2xx status code that handles as an OK response is "200" but some services I am monitoring return status codes of 201, 202, and 206. I used a match as a catch all for the 2xx and 3xx status code ranges.

@aodj
Copy link

aodj commented Mar 26, 2014

Relates to: #224

@PopDaph
Copy link
Collaborator

PopDaph commented May 12, 2014

I agree that 2xx are all successful responses.

For the 3xx, I know that they are all redirections, but I wonder if 310 shouldn’t be considered as an error response. What do you think ?

@cdgraff
Copy link

cdgraff commented May 12, 2014

For example in my case I have a Redir Service only replay 301 or 302 and will be great can monitoring the uptime with this tool, for this reason, can be a Flag if the 30x need to be ok or not? configurable option will be great!

fzaninotto added a commit that referenced this pull request May 22, 2014
Accept all 2xx and 3xx HTTP status codes as successful
@fzaninotto fzaninotto merged commit ae3876c into fzaninotto:master May 22, 2014
@fzaninotto
Copy link
Owner

Thanks!

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 this pull request may close these issues.

5 participants