Page 1 of 1

Global Remote Files Option Error Handeling

Posted: 13 Oct 2014, 16:23
by bfsworks
Hello,

We have run into an issue and I wanted to take the time to suggest this feature as this will help us and possibly other in the future:

We have Global Whitelist file on a remote http server and we love the feature to be able to import a GLOBAL_ALLOW, GLOBAL_DENY, and GLOBAL_IGNORE. The issue we had is our remote http server that hosts our global lists became unavailable and when it came time for the LF_GLOBAL interval to come around the remote file was unable to load and we lost a very important dynamic whitelist.

We have been long time supporters of CSF with monthly contributions and I we would like to suggest a feature that would allow the option in the GUI called something like "Remember Last Downloaded Global List". If checked then if for whatever reason a GLOBAL_* URL was "unreachable" or "empty" or "errored out / 404 / warning / server message with non ip addresses" then CSF would keep the previous successfully downloaded list and log a warning of the recent failed attempt.

In the meanwhile we are going to of course look into some warning or redundancy on our end, however, we think that this issue could happen again for various uncontrollable reasons and would be a fairly easy feature enhancement to CSF and would help users that rely on the GLOBAL_* functionality.

Thank you!

Re: Global Remote Files Option Error Handeling

Posted: 15 Oct 2014, 18:03
by ForumAdmin
lfd should already be doing this. If a GLOBAL_* list results in a failed url request it errors with "Unable to retrieve global
  • list - [REASON]" and the existing list remains intact. The only for that procedure to fail would be if the url request returned a HTTP 200 success incorrectly from the web server hosting the list.

Re: Global Remote Files Option Error Handeling

Posted: 16 Oct 2014, 22:47
by bfsworks
Interesting. We will double check to see if a 200 was issued and we may need to add some better error handling and possibly 404 in the event of issue or page rendering issue. Thank you for this confirmation.