Hello,
the error message posted above indicates the the client wants HTTPS content, but MWG responds with a plain HTTP response because SSL Scanner is turned off. Even if you do not want to use SSL Scanner to inspect traffic I recommend to alway call an "Set Client Context" action, as this will give MWG a certificate which it can use to provide a correct answer.
Example:
- Client requests "https://www.my-forbidden-url.com/".
- MWG sends the URL against URL Filter Database and detects the page should be blocked
- There is no client context, so
- MWG cannot return an error page, because it cannot speak HTTPS to the client
- Therefore it sends a plain HTTP response
- This is not accepted by browsers and will lead to "Page cannot be displayed" or the Firefox error you indicated above.
If you had an "Enable Client Context" action but do not inspect SSL traffic MWG will ONLY use its own certificate for block pages - very helpful when something does not work. In this case you can see why MWG has not made a connection to the website... could be blocked by any filter or even show a "Bad Gateway" or similar response indicating that MWG is not able to talk to the remote website.
Best,
Andre
No comments:
Post a Comment