I'm attempting to fully verify the HTTPS encryption using Chrome & Firefox but both browsers currently display the connection as 'including resources which are not secure'.
I have tried using WireShark to package sniff the wire, but I am unable to determine what is causing this http request, because WireShark detects no traffic as HTTP on the main page.
Here is my .htaccess file for the root domain https://diginomics.com:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://diginomics.com/$1 [R,L]
Notice how some pages such as /about are verified, but the main page is not? Why is this? There must be something simple that needs adjustment.
Also, the HTTPS redirect completely overruled by subdomain which should be on forum.diginomics.com
Good people of Stack Information Security, how can I find where the insecure content is coming from when I am packet sniffing and nothing on the main page comes up as HTTP? What is causing the breach in security on the main page but not on the others?