<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">
<pre class="tw-data-text tw-ta tw-text-small" data-placeholder="Traduction" id="tw-target-text" style="text-align: left; height: 120px;" data-fulltext="" dir="ltr"><span lang="en">Hello,
Thank you for your reply.
ok I will try this beautiful version of Squid 4.
Regards.
Laurent
</span></pre>
<br>
<br>
Le 05/07/2018 à 20:16, Amos Jeffries a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:cefbcdb6-f5f1-cf89-6950-4fb5b5a3ddc1@treenet.co.nz">
<pre wrap="">On 06/07/18 00:49, Laurent Verheirstraeten wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
We have to deal with to a problem when using the function ‘Peak and
Splice’ on the version 3.5.27 of Squid.
</pre>
</blockquote>
<pre wrap="">
Please upgrade to Squid-4.1. It resolves quite a number of annoying
SSL-Bump issues and has far better TLS support than Squid-3.
</pre>
<blockquote type="cite">
<pre wrap="">We tried and set up a transparent proxy, but the rules we declared are
not taken into account because both (squid) server and client are not
using allways the same DNS.
(we’re using a pool off 2 different DNS servers, not using the same cache ).
We’ve noticed that the IP addresses taken into account by the server
Squid and the client are not the same while solving the hostname.
In that special case, Squid sends an error during the ‘Splice’. When the
IP addresses are the same, then the function ‘Splice’ works perfectly.
Is there a way into Squid to specify the same IP address on both sides?
</pre>
</blockquote>
<pre wrap="">
Having Squid use the same DNS resolver as the client makes most
occurrences of this problem go away.
<a class="moz-txt-link-rfc2396E" href="https://wiki.squid-cache.org/KnowledgeBase/HostHeaderForgery"><https://wiki.squid-cache.org/KnowledgeBase/HostHeaderForgery></a>
</pre>
<blockquote type="cite">
<pre wrap="">
Have you already seen that kind of problem ?
</pre>
</blockquote>
<pre wrap="">
Yes. It is a well-known issue with interception proxies.
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>
<p><br>
</p>
</body>
</html>