4 ms·
curl -x http://xxxxx:xxxxx@geo.iproyal.com:11202 http://xxxxx:xxxxx@geo.iproyal.com:11202 -L https://aroma.global.ssl.fastly.net/ https://aroma.global.ssl.fastl
by KomoD 10mo ago
curl -x http://xxxxx:xxxxx@geo.iproyal.com:11202 http://xxxxx:xxxxx@geo.iproyal.com:11202 -L https://aroma.global.ssl.fastly.net/ https://aroma.global.ssl.fastly.net/
<html><body><h1>You don't seem to be using a TCP Proxy!</h1><p>(If you are using a VPN or any other kind of proxy that is not a TCP Proxy, this will not detect it)</p></body></html>
- Sakura-sx 10mo agoThat's strange, could you try with "https://aroma.global.ssl.fastly.net/score https://aroma.global.ssl.fastly.net/score"?
- ranger_danger 10mo agoI got 0.295 with a mptcp'd proxy
- bandie91 10mo agopardon my ignorance but it's a HTTP proxy not a TCP one. is not it? ... or is it considering that https upstream goes through "CONNECT" request?
- JDye 10mo agoA request to a HTTPS target through a proxy will use a CONNECT request to establish a tunnel to the target. This tunnel operates at layer 3, where the client sends TCP segments to the proxy, the server unpacks the segments and then repacks them into new segments to send to the end target. These new TCP segments will contain the timestamp of when they were created. The HTTP request sent through those segments is unmodified, meaning it will contain the original timestamp from the client machine. The newer timestamp on the TCP segments means there is a mismatch between the TCP RTT and the HTTP RTT.