Gah. Even with SWG agent disabled I'm now seeing strange behaviour. If I browse straight to the excluded site, the traffic goes via SecureConnect. No matter how many times I refresh, or how long I leave it, it's always egresses via SecureConnect. If I then ping the site (or tracert, which also pings) I can see the traffic egressing the WAN interface and the website then updates and shows the WAN IP address. It's almost as if some traffic, other than HTTP/HTTPS, needs to pass through before the exclusion kicks in. If I then flush my DNS cache, the traffic reverts back to egressing the SecureConnect IP, until I ping the site. Then it's back to the local WAN IP.
... View more