Using DXA 1.8 (.NET) and Web 8.5 for prod environment and a load balancer to distribute traffic to web servers. The LB hits a simple HTML page to verify that the server is up and that traffic should be sent to that server. This page is on the main DXA website root, and via trace logs administrator sees that the call to the HTML page is being routed to DXA as well. Some snippets from the site.log as below, the requests are also seen in the IIS logging.
TRACE - StaticContentModule.BeginRequest(ASP.global_asax, System.EventArgs) : "/ecv.html" entry. TRACE - CdApiLocalizationResolver.ResolveLocalization(http://HOSTNAME:PORT/ecv.html) entry. DEBUG - Request URL 'http://HOSTNAME:PORT/ecv.html' maps to Localization [5 ('English')]
There is a very high degree of traffic going to this page (ie 30K calls in one day), so admin is asking if it is possible to isolate the ecv page so it isn't processed by DXA. This is the same site check mechanism which had been used on the older non-DXA website.