Ability to set error HTTP statuses (!= 2xx) as "it's ok" #1

EpocDotFr · 2017-09-19T08:19:28Z

Actually, only 2xx HTTP status codes are used to determine that an URL is OK (the white list).

Add a feature to define that, for each monitoring, HTTP status codes other than 2xx are also "OK" (i.e reachable) as the server responded anyway.

Use case: monitoring a website that is protected by HTTP authentication. A request to this kind of resource will return a 401. That is okay because the server response even if it's an error. Also I don't want Server Patrol to be able to store credentials for security reasons.

EpocDotFr added the enhancement label Sep 19, 2017

EpocDotFr changed the title ~~Ability to add any status codes to the whitelist~~ Ability to add "Not OK" status codes to the whitelist Sep 19, 2017

EpocDotFr changed the title ~~Ability to add "Not OK" status codes to the whitelist~~ Ability to set HTTP statuses other than 2xx as "it's ok" Oct 23, 2017

EpocDotFr changed the title ~~Ability to set HTTP statuses other than 2xx as "it's ok"~~ Ability to define HTTP statuses other than 2xx as "it's ok" Oct 23, 2017

EpocDotFr changed the title ~~Ability to define HTTP statuses other than 2xx as "it's ok"~~ Ability to set error HTTP statuses (other than 2xx) as "it's ok" Oct 23, 2017

EpocDotFr changed the title ~~Ability to set error HTTP statuses (other than 2xx) as "it's ok"~~ Ability to set error HTTP statuses (!= 2xx) as "it's ok" Oct 23, 2017

EpocDotFr closed this as completed Oct 23, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ability to set error HTTP statuses (!= 2xx) as "it's ok" #1

Ability to set error HTTP statuses (!= 2xx) as "it's ok" #1

EpocDotFr commented Sep 19, 2017 •

edited

Ability to set error HTTP statuses (!= 2xx) as "it's ok" #1

Ability to set error HTTP statuses (!= 2xx) as "it's ok" #1

Comments

EpocDotFr commented Sep 19, 2017 • edited

EpocDotFr commented Sep 19, 2017 •

edited