Notify.bluecoat.com unexpectedly shows up when using coaching pages

Products

• Cloud Secure Web Gateway - Cloud SWG

Issue/Introduction

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 Edge SWG (ProxySG)

• Access Method: Proxy Forwarding using on-premise Edge SWG (ProxySG)
• Web Security Service (WSS) Content Filtering policy contains Verdict for "Allow with Coach" 

The notify page comes up instead of the coaching page

"You have reached notify.bluecoat.com"

Environment

Proxy Forwarding access method

Cause

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

For customer who used the Web Security Service (WSS) ProxyForwardingCPL you can apply the following CPL as a workaround:

; 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
 
<Forward Cloud> server_url.domain=notify.bluecoat.com
  server_url.query.regex="http/" forward("Threatpulse8443")
  server_url.query.regex="https/" forward("ThreatpulseHTTP8080")