On 4/07/2015 12:05 a.m., Stakres wrote: > Hi Amos, > Can we expect a workaround to allow the object to the cache if the dns > record is corrected by Squid instead that having an ORIGINAL_DST ? > If Squid corrects the request, it mean the URL will be good, so we should be > able to cache the object Any ideas on how Squid could "correct" the request when all data comes from the untrusted client? I am still looking for ways to get per-client caching to operate cleanly. For these (and Cache-Control:private objects) to be stored for re-use by the one client. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
