Notify.bluecoat.com unexpectedly shows up when using coaching pages
Last Updated April 16, 2018
If you are using the following deployment method and configuration, there is a possibility where the user will receive an unexpected coaching page error when using Proxy Forwarding method with ProxySG
- Access Method: Proxy Forwarding using on-premise ProxySG - Web Security Service (WSS) Content Filtering policy contains Verdict for "Allow with Coach"
The notify page comes up instead of the coaching page
Proxy Forwarding access method
"You have reached notify.bluecoat.com"
The issue is related to Web Security Service (WSS) Load Balancing logic. If the origin web request and notify page request are sent to different WSS Datapod, the user will receive a coaching page error as displayed above.
Resolution: Support has raised a bug with Engineering on a permanent solution in future.
You can apply the following CPL as a workaround. ===BEGIN=== ; If you are applying Verdict for "Allow with Coach" in WSS Content Filtering Policy, you must apply; the following policy to set proper forwarding host for notify.bluecoat.com based on server URL scheme