[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Strange TCP connection behavior 2.0 RC2 (+3)
- Subject: Strange TCP connection behavior 2.0 RC2 (+3)
- From: malayter at gmail.com (Ryan Malayter)
- Date: Wed, 29 Jun 2011 05:59:49 -0700 (PDT)
- In-reply-to: <BANLkTin4RBcVAZaz9kwoBouHmT1TBndkbQ_xc9E=OFFx4GEr5w@mail.gmail.com>
- References: <[email protected]> <[email protected]> <[email protected]> <BANLkTi=KuAnuvwXkOi2wU=nXQuuWOLEg3JD3F4xR7uVc-9Gw3g@mail.gmail.com> <[email protected]> <BANLkTi=nbqdV+=ZUvLaiwy_ZHwS_fk79amzFXxYB-ca_MSt7ZA@mail.gmail.com> <[email protected]> <BANLkTin4RBcVAZaz9kwoBouHmT1TBndkbQ_xc9E=OFFx4GEr5w@mail.gmail.com>
On Jun 28, 3:35?pm, Cameron Byrne <cb.li... at gmail.com> wrote:
>
> AFAIK, Verizon and all the other 4 largest mobile networks in the USA
> have transparent TCP proxies in place.
Do you have a reference for that information? Neither AT&T nor Sprint
seem to have transparent *HTTP* proxies according to
http://www.lagado.com/tools/cache-test. I would have thought that
would be the first and most important optimization a mobile carrier
could make. I used to see "mobile-optimized" images and HTTP
compression for sites that weren't using it at the origin on Verizon's
3G network a few years ago, so Verizon clearly had some form of HTTP
proxy in effect.
Aside from that, how would one check for a transparent *TCP* proxy? By
looking at IP or TCP option fingerprints at the receiver? Or comparing
TCP ACK RTT versus ICMP ping RTT?