IS - Less router hops using https versus http based traffic

[kilos]

Some useless info , with different routing
HTTP traffic (TCP port 80) to Woolworths website
tcptraceroute www.woolworths.co.za 80 [16 HOPS]

traceroute to www.woolworths.co.za (165.4.11.99), 30 hops max, 60 byte packets
 1  Router  1.190 ms  1.174 ms  1.162 ms
 2  196-209-0-1.dynamic.isadsl.co.za (196.209.0.1)  10.259 ms  11.467 ms  12.968 ms
 3  196.38.73.85 (196.38.73.85)  125.601 ms  126.984 ms  127.922 ms
 4  [B]cdsl2-rba-vl150.ip.isnet.net (196.38.73.9)  142.727 ms  144.165 ms  144.893 ms[/B]
 5  * * *
 6  * * *
 7  196.38.73.185 (196.38.73.185)  61.485 ms  62.640 ms  64.233 ms
 8  [B]core1a-pkl-te-1-1.ip.isnet.net (196.26.0.60)  66.192 ms  61.497 ms  62.652 ms[/B]
 9  [B]168.209.100.234 (168.209.100.234)  117.548 ms  108.723 ms  109.128 ms[/B]
10  cbm1a-ctn-fa0-0.ip.isnet.net (168.209.2.8)  112.813 ms  114.023 ms  114.945 ms
11  cbm1b-ctn-fa0-1.ip.isnet.net (196.23.188.147)  143.763 ms  144.160 ms  144.446 ms
12  css2-ctn-gi0-1.ip.isnet.net (168.209.2.15)  156.920 ms  157.617 ms  149.274 ms
13  mi-za-cpt-gsrpe1-gi1-0-3-738.ip.isnet.net (196.38.169.101)  107.140 ms  106.844 ms  107.118 ms
14  196.38.121.89 (196.38.121.89)  115.742 ms  120.863 ms  120.818 ms
15  165.4.7.20 (165.4.7.20)  132.989 ms 165.4.7.22 (165.4.7.22)  131.231 ms  131.778 ms
16  165.4.11.99 (165.4.11.99)  132.983 ms  135.541 ms  134.242 ms

HTTPS traffic (TCP port 443) to Woolworths website
tcptraceroute www.woolworths.co.za 443 [13 HOPS]

traceroute to www.woolworths.co.za (165.4.11.99), 30 hops max, 60 byte packets
 1  Router  1.469 ms  1.453 ms  1.441 ms
 2  196-209-0-1.dynamic.isadsl.co.za (196.209.0.1)  11.417 ms  12.020 ms  13.253 ms
 3  196.38.73.85 (196.38.73.85)  130.388 ms  151.352 ms  151.441 ms
 4  [B]cdsl2-rba-vl150.ip.isnet.net (196.38.73.9)  150.448 ms  151.264 ms  151.257 ms[/B]
 5  [B]196.26.0.61 (196.26.0.61)  133.923 ms  135.097 ms  136.078 ms  ---------------DIFFERENT ROUTER [/B]
 6  [B]168.209.100.214 (168.209.100.214)  96.992 ms  80.046 ms  81.183 ms ------------DIFFERENT ROUTER[/B]
 7  cbm1a-ctn-fa0-0.ip.isnet.net (168.209.2.8)  91.006 ms  80.942 ms  81.132 ms
 8  cbm1b-ctn-fa0-1.ip.isnet.net (196.23.188.147)  150.602 ms  150.980 ms  150.340 ms
 9  css2-ctn-gi0-1.ip.isnet.net (168.209.2.15)  144.870 ms  146.337 ms  146.542 ms
10  mi-za-cpt-gsrpe1-gi1-0-3-738.ip.isnet.net (196.38.169.101)  95.019 ms  96.459 ms  99.438 ms
11  196.38.121.89 (196.38.121.89)  102.310 ms  98.909 ms  99.081 ms
12  165.4.7.22 (165.4.7.22)  146.048 ms  158.760 ms 165.4.7.20 (165.4.7.20)  160.603 ms
13  165.4.11.99 (165.4.11.99)  158.796 ms  150.229 ms  151.900 ms

 

[Tinuva]

Thats normal. They are sending port 80 traffic to a transparent caching server. HTTPS are usually encrypted and is counter productive to send that traffic to a caching server.

So that is what you are seeying here. If they use the product I think they use, you can do tcptraceroutes for ports over 1024 as well, that should do the same thing as port 80, ie. go through the caching server, which is able to cache un-encrypted p2p ect. as well. Which is why its a good idea to not enforce encrypted p2p sessions, allow it, but also allow un-encrypted p2p sessions in torrents, that way you can score faster downloads from the caching server.