This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HTTP Scanning issue

I have noticed along with others at my company that when HTTP(not HTTPS) scanning is enabled inside of a policy it essentially breaks the network. For instance with Pandora it would say buffering, then skip to the next song after about 5 seconds.  This would happen repeatedly and never actually play anything. Once HTTP scanning was turned off it started to work again. Any ideas?



This thread was automatically locked due to age.
Parents Reply Children
  • Hi,

    there is the ability to disable scanning on streaming media. There will not be an issue with this because streaming media is not run as an application and has no start or end.

    Ian

  • I'm guessing this is not for all sites but a few? if so it's not usual for this to crop up - I handle them with a specific firewall rule for the destination domain with no HTTP scanning, this is the XG way of putting in a UTM SG type proxy exception (I'm assuming access to these sites is not a problem).

    I think it's just the filtering process is quite strict on the HTTP headers it will process, but that's just a guess on my part.

     

    Regards