Harish Mallipeddi wrote:
Since no one has mentioned this yet, StarHub clearly throttles
bittorrent traffic (at least they did last year). After moving to a
new apartment, I've been using my friend's SingNet broadband and IMO
it's way better than StarHub and they don't seem to be shaping any
bittorrent traffic.
Ya good point. That is true. Starhub is terribly slow for bittorrent.
I tend to bittorent off a slice in the US and VPN it back; the openvpn
UDP is not throttled so it works out faster.
re: iPhone Developer site problem - if you're on SingNet, just setup
the proxy for HTTP(S) to proxy.singnet.com.sg
<http://proxy.singnet.com.sg>. That solves it. This problem occurs
whenever the session management is very strict - it binds the IP
address to the session key. Trac by default is also configured to do
the same.
I guessed it might be something like this - although aren't the caches
and load balancer / layer 4 switches (or whatever the marketing name is
these days) supposed to have sticky IPs for client sessions to handle
this (i.e. use the same cache on subsequent requests)? Maybe they have
don't have this enabled for some reason.
That said I think in the case of Apple, if the sticky IPs is on the
source / dest addr tuple, then this might not be enough as they bump you
through a few different servers and the redirected server may have the
strict IP requirement (you get redirected back and forth through
daw.apple.com and possibly even connect.apple.com).
Another problem we had with the starhub transparent caching is they
didn't support HTTP gets on files larger than 2GB (files would get
chopped off at 2GB mark) - this may have been fixed now... You could get
around be telneting to port 80 on the remote server and sending garbage,
this seemed to disable the transparent cache on subsequent requests (for
a few minutes).
~mc
_______________________________________________
Slugnet mailing list
[email protected]
http://wiki.lugs.org.sg/LugsMailingListFaq
http://www.lugs.org.sg/mailman/listinfo/slugnet
