From 1fb9051ae12be292519821623dc3eef0e3541c24 Mon Sep 17 00:00:00 2001 From: Ben Busby Date: Tue, 28 Dec 2021 12:33:04 -0700 Subject: Broaden HTTPoison status code inspection Rather than enforcing a 200 status code, the instance query is deemed a success if the status code is <400. Various services return 200-399 status codes that don't necessarily indicate an error, but may have to do with how the instance was configured. --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index c8db668..43443a8 100644 --- a/README.md +++ b/README.md @@ -37,8 +37,9 @@ For example: The app runs with an internally scheduled cron task that queries all instances for services defined in [services.json](services.json) every 5 minutes. For each instance, as long as the instance takes <5 seconds to respond and returns -a 200 status code, the instance is added to a list of available instances for -that particular service. If not, it is discarded until the next update period. +a successful response code, the instance is added to a list of available +instances for that particular service. If not, it is discarded until the next +update period. Farside's routing is very minimal, with only the following routes: -- cgit v1.2.3