And like an idiot he realises his error. If you have the DP and MP sharing the Default Web Site then you only have the ability to support HTTPS on the server when the only binding on default web site is HTTPS
Sent from my iPhone > On 7 Sep 2016, at 15:51, Marcum, John <[email protected]> wrote: > > Seems like it should be the other way around: > > Before a client can communicate with a site system role, the client uses > service location to find a site system role that supports the client's > protocol (HTTP or HTTPS). By default, clients use the most secure method > available to them: > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Jason Wallace > Sent: Wednesday, September 7, 2016 9:19 AM > To: jaswall/edarkosarwa/magzparmenter/<Unnamed>/pradeepe > <[email protected]> > Subject: [mssms] DP selection > > Hi folks > > I have 2 systems both configured (as close as I can see it) identically as > both DP and MP. The only difference between them is that one of the systems > is configured as HTTPS for the MP role while the other is HTTP. > > Looking at IIS logs however one of the DPs (the non HTTPS MP) is serving all > content while the other is not. > > Would that be expected? > > Sent from my iPhone > > > > > ________________________________ > > Confidentiality Notice: This e-mail is from a law firm and may be protected > by the attorney-client or work product privileges. If you have received this > message in error, please notify the sender by replying to this e-mail and > then delete it from your computer. > > > > >
