This is an example of how TFS is robust enough to prevent
you doing silly and potentially costly (in terms of time) mistakes.
Let’s say you are configuring a new instance, and you just
got your SSL certificate installed on the machine. So you select the HTTPS and
HTTP option in the configuration settings, and you select your certificate. And
you get an error:
Clicking on that link creates the correct bindings for that
certificate. Fair enough.
But the Public URL is not what you like, so you change it to
something else. And you go ahead.
The result?
The readiness checks prevent you from doing this. It also
checks for SNI validity amongst the other things, something that comes handy
when you deal with Chrome.
No comments:
Post a Comment