Too many SSL connect for OPTIONS Request - CORS in Azure Kubernetes Cluster

Hi rs232,

what makes me wonder is that during the SSL negotiation only the User-Agent may know that the SSL channel will be later used for one of those OPTION requests. Hard to imagine that it could be a server side problem...

What happens if you plug a SSL inspection forward proxy (e.g. fiddler) in the communication? 

Using Wireshark with TLS inspection would be my next attempt to figure out what's happening on the wire during those negotiations? 

Cheers, Kai