Matching rule not matching expected traffic [URL categorisation]

book

Article ID: 166720

calendar_today

Updated On:

Products

PacketShaper

Issue/Introduction

When running Packetwise version 8.6 or greater, you may see that a class is reporting less class hits than expected, and when using the host analysis tool is matching the incorrect class.

When creating any matching rule, there is a "URL Category" dropdown, wherein any setting supplied other than "Any" requires that the traffic to match this class be recognised as belonging to at least one URL category.

Resolution

When classifying traffic, and establishing a configuration where one is not certain that the traffic will belong to a URL category, the URL category dropdown must be set to "Any". The "All Categories" configuration option will exclude traffic which we cannot find a category for (non-http, http tunneled traffic, SSL-No-Cert).