Cisco Bug: CSCup13935 - Enhancements for local profiling in case of FlexConnect Local Switching
Feb 05, 2019
- Cisco 5500 Series Wireless Controllers
Known Affected Releases
Symptom: #1. Requesting support of subsequent HTTP packets which may contain different user_agent information than first HTTP packet. By current design, FlexConnect-LocalSwitching APs copy and transfer only first HTTP packet to its WLC. Customers Windows7 clients in an Internet proxy server environment are tend to use GET proxy.pac in the fist HTTP packet which contains following user agent; Mozilla/5.0 (compatible; MSIE 9.0; Win32; Trident/5.0) Since it is "Win32" which cannot be profiled properly as "Windows7", the client profile result stays as "Microsoft-Workstation" which has been obtained by DHCP classid (MSFT5.1) prior to the HTTP packet for proxy.pac. Subsequent HTTP packets are not used for re-classify even if it contained following correct more accurate information. Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) "Windos NT 6.1" stands for "Windows7". This is because FC-LS AP is not going to copy nor transfer this subsequent HTTP packet to WLC. #2. Requesting support of TCP port number 8080 which is used as a TCP HTTP Alternate. In order to support clients using HTTP proxy in FC-LS environment, Request#1 is not sufficient. Since the client often uses TCP port# 8080 for HTTP communication after GETting the proxy.pac, we need to add TCP port# 8080 to the target packet to be copied and transferred by FC APs. Conditions: Local profiling. WLAN is enabled for HTTP local profiling. FlexConnect LocalSwitching mode AP. Internet proxy sever is used for HTTP communication. Client is using other than #80 for HTTP communication.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases