Steps to reproduce the problem:
1) We are working on enabling our android app to handle http/https links. And for that  we are using intent filters in our app manifest to declare the URI patterns that your app  handles.
The following example shows an intent filter that can handle links to http://www.example.in and https://www.example.in:

            <intent-filter>
                <data android:scheme="http" />
                <data android:scheme="https" />
                <data android:host="www.example.in" />
                <data android:pathPattern=".*" />
                <action android:name="android.intent.action.VIEW" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
            </intent-filter>

2) As per chrome implementation when navigating within the same host it will show an Intent App Chooser if there is a newer App available to handle the target url as compared to the apps which can handle the source/referrer url. 

Source Code Link : https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/externalnav/ExternalNavigationHandler.java?q=browser_fallback_url&sq=package:chromium&l=385

Essentially this means that when user navigates from a not-handled-in-app-url to a handled-in-app-url within the same host, chrome will show the Intent App Chooser. 

3) In the intent filter i mentioned above, we are handling all the http/https links with domain name example.in. So while navigating with in the same host (ie : www.example.in) , there should not be any intent app chooser since both source and target pages are registered in the Android Manifest.

4) We are facing an issue while navigating between https to http pages in Android Google Chrome. Let me explain the issue in detail.
i) Source  : http://www.example.in/sourcepage 
   Target  : http://www.example.in/targetpage
   As you can see both source and destination pages are http and are also whitelisted in the Android Manifest. The expectation is not to open the Intent Handler and it works fine.

ii) Source  : http://www.example.in/sourcepage 
    Target  : https://www.example.in/targetpage
    Here source page is a http page and destination page is https page. Both pages are whitelisted in the Android Manifest.And it works as expected by not showing intent chooser.

iii) Source  : https://www.example.in/sourcepage 
    Target  : https://www.example.in/targetpage
    Here both source destination page are https. Both pages are whitelisted in the Android Manifest. And even in this case it works as expected by not showing intent chooser.

iv) Source  : https://www.example.in/sourcepage 
    Target  : http://www.example.in/targetpage
    Here source page is a https page and where as destination page is a http page. Both pages are whitelisted in the Android Manifest.
    And the expectation here is not to show intent chooser.
    But in this case an Intent Chooser is shown.

We feel that this unexpected behaviour is an issue with google chrome. 
Can you please take a look at it and let us know that when can we expect the fix ?
If there is any workaround you can suggest us to solve this issue, please let us know.

What is the expected behavior?
Intent Chooser should not be shown while navigating from https to http pages (Both the source and target pages are whitelisted in android manifest and belong to the same domain).

What went wrong?
Intent Chooser is shown while navigating from https to http pages (Both the source and target pages are whitelisted in android manifest and belong to the same domain). 

Did this work before? No 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 6
Flash Version: 

We feel that this unexpected behaviour is an issue with google chrome which is affecting the end user experience. 
Can you please take a look at it and let us know that when can we expect the fix ?
If there is any workaround you can suggest us to solve this issue, please let us know.