Skip to content

Conversation

@TimZ99
Copy link
Member

@TimZ99 TimZ99 commented Aug 29, 2018

Closes #175.

Added the option to mark specific HTTP status codes as online. 401 and 403, for example, don't mean that the server is offline.

@TimZ99 TimZ99 merged commit 7aa7ec3 into develop Sep 5, 2018
@TimZ99 TimZ99 deleted the feature/175 branch September 5, 2018 20:34
@SciLor
Copy link

SciLor commented Sep 9, 2018

I have configured the "400" as allowed. But it still fails on "HTTP/1.1 400 Bad Request".

@TimZ99
Copy link
Member Author

TimZ99 commented Sep 12, 2018

Doesn't the check fail because of another test?
If I test a website with a 400 error, it marks it as online.

@SciLor
Copy link

SciLor commented Sep 12, 2018

I am sure, that it didn't worked because of that. It is a POST in my case. The other check was for a special text. If I inverted the rule (text not in) it still failed, but because of the text. I will log that for you later on.

@SciLor
Copy link

SciLor commented Sep 12, 2018

If pattern is set as offline, Last error shows "TEXT ERROR : Pattern '344' was found."
If I switch it to online it stays on that last error.

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