Ask
Reply
Solution
08-09-2009 08:33 AM
08-09-2009 05:35 PM
08-09-2009 10:56 PM
08-09-2009 11:23 PM
Why is it that during loading of pages like telegraph.co.uk mobile broadband sticks at google-analytics.com. This is not the only one but many pages access external advert sites and these don't seem to be welcome.
08-09-2009 11:40 PM
10-09-2009 06:49 AM
I don't know in great detail exactly how web-traffic works, but given that Vodafone has NAT routing (and it's transforming proxies), I wonder whether all of all Vodafone's mobile broadband customers appear to external websites to be one very very active customer (all coming from a single, or very small set of IP addresses) and whether those websites' servers limit the total number of connections per customer/IP ... which might cause bottlenecks with popular sites...?
10-09-2009 08:41 AM
That's a good theory there techmind. The IP's are shared, using both NAT and PAT, so the affected websites could very well be employing "anti-hammering" techniques on Vodafone customers.
That problem will go away as soon as we switch to Public IP addressing, but it's something I don't think we've taken into account before. The problem is going to be figuring out a way to test it.
Jon
eForum Team
11-09-2009 08:36 AM
That's a good theory there techmind. The IP's are shared, using both NAT and PAT, so the affected websites could very well be employing "anti-hammering" techniques on Vodafone customers.
28-09-2009 11:13 PM
Then again, you might expect that Vodafone's cacheing servers/proxies would greatly reduce the traffic seen by the external websites if this were in fact a potential problem - though the cacheing may be less effective if the sites are substantially dynamic and can't be cached properly.
On the other hand, if too many Vodafone customers are hitting ctrl+F5 and/or using Firefox with "no-cache" header modifications (to circumvent Vodafone's image-compression) then VF cacheing will be less effective and a lot more "duplicate" traffic requests will be put out onto the internet... Another reason to hurry up and get rid of the compression/"transformation" proxies?