Originally Posted by rdhw
This is a commonly reported problem with the transparent web caches.
A minor point, but actually it may not be a problem with the caches per se but rather an issue with the local transparent cache redirection mechanism e.g. Cisco's WCCP routers or Layer 4/7 switches.
Naturally the proxies are more tangible and usually get blamed first. Specifying a direct proxy will 'fix' the issue temporarily until the cache's ip address changes or it is unavailable.
Of course ntl can't investigate these problems unless they know which location is affected.