I've noticed a strange behavior when enabling HTTPS inspection, would like to confirm if anyone has seen a similar problem?
When HTTPS inspection is enabled, page blocking by categorization takes much longer to apply. For e.g. when accessing betting sites over HTTPS or pages with image galleries, the page loads fine and its contents load. Smartview Tracker shows the page contents as blocked but they are loading fine on browser. After retrying approx 30 seconds to 1 minute later, the page is then correctly blocked and Usercheck page is shown.
Is it normal for categorization to take longer on HTTPS inspection or for pages to load successfully for so long? Is there any way to troubleshoot what is happening to cause this delay?
Without HTTPS inspection, pages are blocked almost instantly. Maybe the first time they load partially (images etc don't load) but immediately after the first refresh they are fully blocked (no Usercheck which is normal). With HTTPS inspection, even after the first few refreshes the pages still load. This has been tested with various sites and different categories and the behavior is same.