You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Georg Henzler (Jira)" <ji...@apache.org> on 2020/07/08 16:50:00 UTC
[jira] [Resolved] (FELIX-6300) Make avoid404DuringStartup=true the
default for ServiceUnavailableFilter
[ https://issues.apache.org/jira/browse/FELIX-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Georg Henzler resolved FELIX-6300.
----------------------------------
Resolution: Fixed
[~bdelacretaz] you are right, it would have been better to make it the default from the beginning. Fixed in [1a573e93f797|https://github.com/apache/felix-dev/commit/1a573e93f797b5a281e72c079a1b519c509c3f18]
> Make avoid404DuringStartup=true the default for ServiceUnavailableFilter
> ------------------------------------------------------------------------
>
> Key: FELIX-6300
> URL: https://issues.apache.org/jira/browse/FELIX-6300
> Project: Felix
> Issue Type: New Feature
> Components: Health Checks
> Affects Versions: healthcheck.core 2.0.6
> Reporter: Georg Henzler
> Assignee: Georg Henzler
> Priority: Major
> Fix For: healthcheck.core 2.0.8
>
>
> bq. To me, getting a 503 as soon as HTTP requests work is the natural behavior, getting a 404 first and later a 503 is an unfortunate side effect of the HTTP whiteboard.
> (from https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=17060971&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17060971 )
--
This message was sent by Atlassian Jira
(v8.3.4#803005)