-
Notifications
You must be signed in to change notification settings - Fork 6
HTTPS Checker Usage Examples
Andrew Stilliard edited this page Mar 21, 2017
·
5 revisions
With any of these examples the report will show all mixed content issues found. With these you will then need to track them down and fix them.
E.g. a development / staging version of a site.
- Enter the URL of the site (or upload the CSV of URLs).
- Open the advanced options menu.
- Un-tick "Use Robots.txt File Rules"
- Also consider selecting a different User Agent if the site also blocks requests it believes are bots.
- Click Run to begin.
- Enter the URL of the site (or upload the CSV of URLs).
- Select "Chrome Not Secure Warning" as the Mode.
- Click Run to begin.
- Enter the URL of the site (or upload the CSV of URLs).
- Open the advanced options menu.
- Select "Session" and this page will guide you through the process.
- The basic flow for this is to login as a user on your site, grab the cookies the site uses to identify them, and then paste these cookies back into the app. If you have any problems setting this up, please contact us here.
- Click Run to begin.
- As an aside note, an alternative solution that works well for these logged in areas is to use our HTTPS Reporter tool which receives reports automaticaly as users browser sites.
We also have a video available here: https://www.youtube.com/watch?v=fn1lBr9Pggk
Any further questions can be submitted to us here as Issues.
Looking for the desktop checker? Download it here.
Looking for the online reporter? Find it here.