On the surface it looks like they don’t do dpi (deep packet inspection). That is until they flag you as having a bot, then it changes if they inject notifications. Take a look at S4.1.5. and C5.2 in the CC document.
http://www.packetizer.com/rfc/rfc6108/
Excerpt
S4.1.5. Session Management Broker (SMB ): A Load Balancer (LB ) with a
customized layer 7 inspection policy is used to
differentiate between HTTP and non-HTTP traffic on TCP
port 80, in order to meet the requirements documented in
Section 3 above. The system uses a LB from A10 Networks.
The SMB functions as a full stateful TCP proxy with the
ability to forward packets from existing TCP sessions that
do not exist in the internal session table (to meet the
specific requirement "Must Handle Pre-Existing Active TCP
Sessions Gracefully"). New HTTP sessions are load balanced
to the web proxy layer either transparently or using source
Network Address Translation (NAT [RFC3022]) from the SMB.
C5.2. Session Management: TCP port 80 packets are routed to a
Session Management Broker (SMB ) that distinguishes between
HTTP or non-HTTP traffic and between new and existing
sessions. HTTP packets are forwarded to the web proxy by the
SMB. Non-HTTP packets such as instant messaging (IM) traffic
are forwarded to a TCP proxy layer for routing to their
destination, or the SMB operates as a full TCP proxy and
forwards the non-HTTP packets to the destination.
Pre-established TCP sessions on port 80 are identified by the
SMB and forwarded with no impact.
Those sections tell me all I need to know about CC and dpi.
