Sounds to me like they have implemented a non-HTTP protocol over the
HTTP port. Not a proxy friendly thing to do. Your best bet, if you
can't convince them to move their non-HTTP protocol off of the HTTP
port, is to bypass the cache for the offending site. You don't need
individual client rules... Just don't redirect any traffic destined for
the IP in question to the cache. They'll be routed directly for those
requests.
Net Vision Administration wrote:
> I am running Squid 2.2 as a transparent proxy, but have a couple of
> clients using specialised Web Sites and pages for stock quotes. The page
> is static, but the quotes appear in various fields within the web page
> and are changed ever 10 minutes.
>
> It appears the incoming data is sent to Squid's IP address, as that is
> the IP address that originally requested the page, but with this
> constant incoming data, Squid does not know what to do with it, as it
> has already sent the originally requested page back to the clients
> concerned.
>
> Is there anyway I can change the config within Squid to recognise where
> this constantly changing incoming data should be sent to, so as I don't
> have to construct individual routing tables for each client.
>
>
>
> Thanks;
>
> John McGill
--
Joe Cooper <joe@swelltech.com>
Affordable Web Caching Proxy Appliances
http://www.swelltech.com
Received on Thu Mar 22 2001 - 21:48:19 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:58:48 MST