 | 1 | initial version |
The TLS sessions are proxied. Normally when there is a proxied connection over port 8080 or so, ou are able to see the "CONNECT <xxx.xxx.xxx>", the "HTTP/1.1 200 OK" and then the following packets would be shown as TLS, but since this proxy connection is using port 443 as proxy port, Wireshark seems to get confused.
As a workaround, you can disable the HTTP protocol dissector, which will expose the TLS decoding for the TLS part of the proxy connections.
