Suggested sites does not work when site is only available on SSL

Fixed Issue #14556525


Mark H.
Nov 7, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Say for example that examplesite.local is only available on SSL. If you -type- in https://examplesite.local the site is remembered as suggested sites. Now if you close and reopen Edge the site is suggested when you start typing part of the url but Edge wants to navigate to the site on http:// instead of https://. This was not the case in Edge 15.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Hi,

    Is this problem only for localhost sites?


  • I have this issue on both intra- and internet sites


  • Thank you for the quick response.  I will see if I can repro this.

    Also, since you were testing with localhost as well, I take it you only had port 443 listening?

  • I just tried to repro this using a site that states they only support https and even explains why they only support https and why everyone should do the same.  :-)

    I verified the site was not performing a redirect.  However, it appears they are using HSTS and so is probably not the best test case as the .gov domain is most likely in a pre-loaded HTTPS list.

    Can you test using the site above and let me know if you see the same issue?

    I will try two more test cases:

    1. Typing in HTTPS for a site that supports both.
    2. Typing in HTTPS for a site that only supports HTTPS but not HSTS.  I may just create a local test for that.


  • Hi Steven,
    This first time I noticed it is was on an intranet site. I did not test this on a localhost but I also experienced the issue on internetsites. These are indeed site only listening on 443, not 80. Also these sites do not have HSTS set, I don’t think this is part of the issue.
    The other day I also found an issue related to the original issue. Say you have a website running on a different port, say 8080. If you go the site (for example http://examplesite.local:8080) and the webserver is not running you get a page not found (leave Edge open). This is expected behavior. Next start the webserver and wait for it to come online. If you press F5 in Edge it doesn’t understand what to do and opens the default search engine. I’ll try to make some PSR’s to make it a little bit more clear.

  • The PSR did not really make it clear so I made (extremely slow) gif of the original issue, see attachment. Als notice when I open Edge the 2nd time when I just type in the “i” an icon appears in the url bar indicating a history item has been found. When I type the “p” the history icons disappears and the search icon shows up.
    Does this make it a little bit more clear?

  • Thank you for the gif.  That is very helpful and clear.  I need to run test #2 I outlined previously to repro this.

    Also, the other issue with the F5 not-recovering would be a separate issue, don’t you think?  Feel free to submit that as a new ticket.

    Appreciate the help,


  • Steve,

    I’m still on build 16.16299 but somehow this issue is now resolved? Both on my work and private laptop.


  • Hi Mark,

    This ticket is still open.  I just have not been able to get back to it.  Does it show that it is closed or resolved?

    I will work on it in the next day or so.  Apologize for the delay.

  • Microsoft Edge Team

    Changed Status to “Fixed”

  • Hi Mark,

    I found a good repro site.  I also wanted to let you know that this has been fixed and is available in 16299.248.  Let me know if you do not see the same results.

    The is the site I used for my testing:

    There are a couple more SSL only test sites referenced in the following post:

    Appreciate your patience and for reporting this,


You need to sign in to your Microsoft account to add a comment.

Sign in