We'd love to hear about it! Click here to go to the product suggestion community
Please see the below pic as I am confused and cannot identify the root cause for this particular XG appliance.
I can see that is is a rule's Web Policy that is triggering this man in the middle type thing, but why only recently? Other sites of https seem fine and show their own correct CA issuers etc.
Like I say, as soon as I take out the Web Policy from this rule (which is not HTTPs scanning/decrypting) it pops up.
The Web Policy does have a custom category in it.
As I say though it was working previously.
Policy tests are 100% OK too.
The appliance is on SFOS 17.5.3 MR-3
Removed, and re-added the URL to the custom web category Domain/URL box and it works.