https certificate mismatch

[Alexandre Machado]

I have a client who wanted https, so they sent me their certificates to test with.

When I test on my local machine my browser tells me that 127.0.0.1 is not the same as the URL in the certificate.
Fair enough - 127.0.0.1 is not the URL.
If I create an exception for 127.0.0.1 it works - albeit with a not secure warning.

So I shipped it to the client.

The issue that the client is having is the same issue.
The URL is resolved into an IP address, and then the browser is saying that the IP address is not the same as the URL.

Is there some property that I have not set correctly? or there something not set up correctly on their server?

In order to run a proper test, edit your Windows hosts file (typical path is "C:\Windows\System32\drivers\etc\hosts").

Add one entry to it like:

    127.0.0.1    thedomain.com

Now, every time you try to access "thedomain.com", you will be redirected (by Windows itself) to 127.0.0.1 which will hit your application.

Have in mind that some AV software won't let anyone edit the hosts file, so you might have to disable it before. Also, remember to undo this change otherwise you won't be able to access the real "thedomain.com" later on.

This is the easiest and recommended way to test a real certificate in your development machine.

Now, back to your question. IW does not redirect from host to IP address internally, unless you have changed a few default configurations in a very unusual way.

I recommend you to run the test above as I mentioned and see how it goes.