Application Request Routing (ARR) - SecureConnectionIgnoreFlags support

Frank Cheung 0 Reputation points
2025-02-11T00:31:59.08+00:00

Hello.

I have ARR 3.0 installed and I want to set the SecureConnectionIgnoreFlags to ignore expired certificates for health checking as described in https://learn.microsoft.com/en-us/iis/extensions/configuring-application-request-routing-arr/arr-support-added-for-winhttpoptionsecurityflags

This article indicated that there's a hotfix for ARR 2.5, https://www.microsoft.com/en-us/download/details.aspx?id=35827 and this hotfix won't install on ARR 3.0

I added the registry setting but it doesn't seem to work.

I also found this KB, https://support.microsoft.com/en-us/topic/june-2016-hotfix-for-microsoft-application-request-routing-3-0-8855fd9c-1d0c-7704-f10b-de18e6efa9b1 but the download link is broken.

Can someone confirm if SecureConnectionIgnoreFlags is supported out of the box w/ ARR 3.0?

Thanks a lot.

Windows development | Internet Information Services
{count} votes

2 answers

Sort by: Most helpful
  1. Frank Cheung 0 Reputation points
    2025-02-11T16:21:42.99+00:00

    Hi.

    The server is running Windows 2022 and IIS 10. ARR version is 3.0.

    Here's a screenshot of the registry. I restarted IIS after inserting the registry value

    User's image


  2. Tom Tran (WICLOUD CORPORATION) 10 Reputation points Microsoft External Staff
    2025-07-07T07:11:55.78+00:00

    Hi Frank Cheung,

    I know this is a really late response.

    From what you've provided, the registry key is correctly configured but ARR 3.0 does not reliably honor SecureConnectionIgnoreFlags out of the box. This behavior was addressed in a June 2016 hotfix (KB3167810), which specifically adds support for this registry setting in ARR 3.0.

    This means that unless the hotfix is already installed, ARR will continue to reject expired certificates during health checks even if the registry key is present. That would explain why traffic initially flowed to the node with the expired cert (possibly due to caching) and then stopped after a few hours, resulting in 502.3 and 503.4 errors.

    In the meantime, you could try:

    1. Small fixes like:
    • Try a different browser (e.g., Edge, Chrome, Firefox).
    • Disable browser extensions like ad blockers or script blockers that might interfere with the download.
    • Use a private/incognito window to bypass cached sessions or cookies.
    • Check network restrictions — some corporate firewalls or proxies may block Microsoft download domains.
    1. Run this PowerShell command to check if the hotfix is installed yet:
    Get-HotFix -Id KB3167810
    
    1. If none of that work, you can still directly request the hotfix by contacting Microsoft since the link to the hotfix is broken: (https://support.microsoft.com/en-us/contactus)
    • Sign in with you Microsoft's account and select "Windows" as the product.
    • In the description, you can state the following for example: “I’m requesting hotfix KB3167810 for Application Request Routing (ARR) 3.0. The public download link is no longer available. This hotfix is needed to enable support for the SecureConnectionIgnoreFlags registry key, which is not being honored in the base version of ARR 3.0.”
    • Proceed with "Contact Support" request via chat or email if available.

    I really hope this solves your issue. Let me know if you require more help!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.