Hi Adrian,<br><br>Thanks for the info, I was thinking that squid-users might be more helpful. For what its worth we dont cache HTML only large files/images etc but I hadn't thought about the "views" issue.<br>
<br>Thanks for your help<br><br>Regards<br><br>Tristram<br><br><div class="gmail_quote">On 20 May 2010 12:45, Adrian Chadd <span dir="ltr"><<a href="mailto:adrian.chadd@gmail.com">adrian.chadd@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 20 May 2010 07:55, Tristram Cheer <<a href="mailto:tproxy@tristramcheer.com">tproxy@tristramcheer.com</a>> wrote:<br>
> Is there anyway to get squid and TPROXY to spoof DNS requests to show as<br>
> coming from the client IP and not cache the result?<br>
<br>
</div>With a bit of coding, sure. This has an impact on your cache contents<br>
- since each client has a "different view" of DNS, content is going to<br>
have to be cached according to the client themselves rather than just<br>
globally. Also, cached content for client A that isn't filtered by<br>
open DNS will be returned to client B that is filtered by open DNS<br>
because cached content doesn't necessarily require constant<br>
revalidation, and cached content w/out revalidation won't require a<br>
DNS lookup to complete. That'll require further code changes.<br>
<br>
You should bounce further questions like this to the squid-users@<br>
list, rather than this list!<br>
<font color="#888888"><br>
<br>
Adrian<br>
</font></blockquote></div><br>