Traffic Not Matching A Custom URL Category With Port Number

• The user configured the following as a custom URL category similar to below:

A.B.C.D:8081/login.shtml

• However, the traffic doesn't match the security policy configured to match this category. 
• URL logs show the URL exactly as configured but categorized as "unknown" and hence traffic blocked. 

• Palo Alto Firewalls
• PAN-OS 8.1 and above
• URL Category

• When the firewall sends a URL category request to the Palo Alto URL Database, it strips out the port number. 
  The port number is used only in the Get request.

1. Configure the custom URL category without the port number when using alternate ports other than 80 or 443.
2. For example, in this case, configure the following: