Hi All -
This issue is driving me nuts, I'm getting mixed content warnings only when accessing certain tools in the site settings menus, otherwise everything else is working - here's the scenario :
- SharePoint 2013 3-tier farm behind an NLB providing SSL termination. Client requests via HTTPS, SSL is decrypted and forwarded by the NLB to IIS as HTTP. Original header intact.
- IIS website is configured as HTTP, catch-all with no host-header, listens on :80
- Web application contains host named site collections. Created via Powershell as follows :
$webApp = New-SPWebApplication -Name $webAppName -ApplicationPool $webAppPool -ApplicationPoolAccount (Get-SPManagedAccount $iisAccount) -AuthenticationProvider (New-SPAuthenticationProvider –UseWindowsIntegratedAuthentication) -Path $path -URL $rootUrl -HostHeader $hostHeader -DatabaseName $dbName
- A root site collection as created (path-based of course) as follows :
$spSite = New-SPSite -Url $url -OwnerAlias $owner1 -SecondaryOwnerAlias $owner2 -ContentDatabase $dbName -Name $name -Template $template -Language $lcid
- Host names site collections are then created similarly, except using the -HostHeaderWebApplication parameter. HNSCs seem to be working just fine, they're accessible through the NLB and appear to work just fine...
...except certain tools in the site settings menu, where I get a mixed content warning - for example :
- Content & Structure gives me a mixed content warning. The browser console tells me it's trying to open
http://<host>/_layouts/15/1033/styles/corev15.css
and
http://<host>/_layouts/15/1033/styles/SiteManagerCustomStyles.css
I get similiar errors for some ribbon controls, for example the Site Collection Administrators tool which wants to open this via HTTP:
http://<host>/_layouts/15/mngsiteadmin.aspx?IsDlg=1
Many other tools in Site Settings work just fine.
Now, I've tried the following :
- I tried doing everything the opposite way around. Created the web application with SSL enabled. Created the root site as HTTPS, created the HNSCs as HTTPS. Added a secondary URL to the HNSCs via PowerShell as HTTP (Intranet Zone). Configured IIS to listen to :80. This actually works, but has exactly the same errors with Content & Structure etc. In other words no change.
I'm not sure what else I can try.
Has anyone got any experience with this issue?