2

We thought it would be a good idea to enable the health check feature for our Episerver ASP.NET MVC web application in Azure. However, after doing so, the number of requests resulting in a 404 immediately rose dramatically for the path specified. The URL is internal. It works fine when browsed to. Any input on what could be the problem greatly appreciated.

Andvik
  • 119
  • 1
  • 12
  • 2
    What do you mean with *The URL is internal.*? – Peter Bons Nov 22 '21 at 07:27
  • What URL is it? Do you mean "internal" as in part of the CMS? Or behind login? – Ted Nyberg Nov 22 '21 at 13:49
  • What I meant with "internal URL" is only that it is not publicly accessible. It points to a start page in the CMS though. – Andvik Nov 22 '21 at 15:10
  • What happens if you browse to the URL without being logged in? – Ted Nyberg Nov 23 '21 at 11:22
  • Good question. Could have been a (silly) issue. But it works fine browsing to the URL in incognito mode. – Andvik Nov 24 '21 at 12:09
  • Are you still seeing 404 errors for that URL, despite being able to browse to the it without being logged in? – Ted Nyberg Nov 24 '21 at 12:54
  • Yes. As strange as it seems that is the case. However, I don't know for sure from where the failing requests come. I can't see the IP nor the user agent due to "GDPR". All we know is that the 404s skyrocketed after enabling the health check and that ALL requests to the specific URL fails with that result code (except my manual attempts). – Andvik Nov 25 '21 at 14:47
  • I encounter the similar issue, did you managed to resolve it? @Andvik – Aruni Mishra Aug 01 '22 at 13:11
  • @AruniMishra No, we eventually gave up and disabled the health check feature :/ – Andvik Aug 03 '22 at 10:52

0 Answers0