<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#464646" bgcolor="#FFFFFF">
<font face="Arial">Amos, <br>
<br>
Thank you for your response and kindness, <br>
I'm turning to create a DNS resolution dev and I'm giving up
looking retreive this information through Squid.</font><br>
<br>
<div class="moz-cite-prefix">Le 16/09/2021 à 19:13, Amos Jeffries a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:deff363e-398f-bb7d-0211-fd762c6f8b4b@treenet.co.nz">On
17/09/21 2:42 am, David Touzeau wrote:
<br>
<blockquote type="cite">Thanks Amos for quick answer.
<br>
<br>
Can you take away any hope of a workaround with Squid ?
<br>
<br>
This makes me plan having to develop a function that has to
perform DNS resolution inside the helper with the performance
consequences that this will impose.
<br>
<br>
</blockquote>
<br>
I would be looking at a design where a helper classifies requests
and using that later on when the server is known to match up the
IP vs the classification. I'm struggling to think of a flow that
works efficiently though.
<br>
<br>
Amos
<br>
_______________________________________________
<br>
squid-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
<br>
</blockquote>
<br>
</body>
</html>