So ... not a big issue in the overall scheme of life - but I've been noticing that ( with current dynamic updates and running 8.1.2) that URL filtering has started to mess up the Amazon-instant-video application. If URL filtering is enabled - the application basically refuses to run - even though NOTHING in URL filtering settings should be effecting it and nothing is apparent by looking at the URL filtering logs.
Interesting to note that in the the traffic logs -the application is not classified properly when URL filtering is on as well ( probably because it's not seeing enough of the exchange to classify the app) - What should be identified as Amazon-instant-video to port 80 simply gets defined as web-browsing to port 80.
It's probably something silly that has changed recently - but for the life of me - I can't see why this would be happening. Nothing else is even looking at the traffic ( I isolated the source addresses and allowed everything through with no inspection other than URL filtering applied).
Any suggestions appreciated,
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!