<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#464646" bgcolor="#FFFFFF">
<font face="Arial">Thanks for the clarification and I agree with you
completely.<br>
<br>
a multipath and a round-robin DNS method will return different
records between our DNS calculation and the final squid results<br>
<br>
It is true that it would be possible to use an external_acl in the
http_reply_access. <br>
<br>
Do you think that adding it in this position I would be able to
use squid's resolution results ?<br>
<br>
<br>
</font>
<div class="moz-cite-prefix">Le 16/09/2021 à 19:43, Alex Rousskov a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:a384aa07-11ac-0801-9a5a-4d6addc8a886@measurement-factory.com">
<pre class="moz-quote-pre" wrap="">On 9/16/21 1:30 PM, David Touzeau wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I'm turning to create a DNS resolution dev and I'm giving up looking
retreive this information through Squid.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Please note that if you do your own DNS resolution, then Squid DNS
resolution results will probably mismatch your results in some cases.
There have been many complaints about associated problems from folks
that went this route...
I am not sure what you are trying to do with that a %<a-based external
ACL in Squid, so it is difficult to narrow down the solution search
scope, but Squid does support slow ACLs in certain directives used when
talking to origin servers or peers (after built-in DNS resolution and
destination selection) so perhaps there is a way to do what you want
without Squid modifications.
If there is not, it would not be difficult to add a post-resolution
directive that supports slow ACLs IMO, but, again, that requires more
knowledge of the use case -- there are several places where such a
directive can be added.
Cheers,
Alex.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Le 16/09/2021 à 19:13, Amos Jeffries a écrit :
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 17/09/21 2:42 am, David Touzeau wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Thanks Amos for quick answer.
Can you take away any hope of a workaround with Squid ?
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.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
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.
Amos
_______________________________________________
squid-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
squid-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
squid-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
</pre>
</blockquote>
<br>
</body>
</html>