Fix appconnect time problematic accumulation when using TLS-in-TLS proxy #7274
Follow up this email list thread.
My commit changes t_appconnect to only record the time that TLS has been established to destination, as both TLS connection finished.
I know we accumulate some timerid because of redirection, any suggestion would be welcome if there's anything is wrong with this PR. :-)
I tested by building locally and the appconnect time is less than all the following time.
Introducing a 'isproxy' argument to the connect function so that it knows wether to store the time stamp or not. Reported-by: Yongkang Huang Fixes #7274