For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jari_Hyttinen_1's avatar
Jari_Hyttinen_1
Icon for Nimbostratus rankNimbostratus
Jun 03, 2013

HTTPS monitor with SNI support

We have published a SharePoint 2013 environment with several applications installed on SharePoint.   Both client ssl and server ssl profiles are in use in all VIPS.   SharePoint use SNI (Serve...
management
monitoring
Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
Jun 03, 2013
So you're doing SNI on the SERVER SIDE?

 

 

If so, I believe an external monitor with cURL is still your best bet. The one trick is that you have to use the server's name in the request instead of the IP address. For this you'll either need a Hosts entry on the BIG-IP or DNS resolution. If you can be in a position to watch the SSL traffic to the web server, you should see cURL's TLS CLIENTHELLO message with a Server Name Indication extension value near the bottom of the payload.