On 22/01/20 12:10 pm, Amos Jeffries wrote:
On 22/01/20 6:55 pm, Amish wrote:
It appears that it runs a query on "counters". But I dont know if that
is counted as a "heavy" query or not.
It is one of the light ones. So if that were all that is going on I
would not be expecting a problem.
...
On 22/01/20 6:55 pm, Amish wrote:
> On 21/01/20 9:09 pm, Alex Rousskov wrote:
>> On 1/20/20 11:28 PM, Amish wrote:
>>
>>> 2) Is calling squidclient so frequently a right thing to do by netdata?
>> The answer depends on what cache manager query (or queries) your netdata
>> is sending to Squid. Sendi
On 22/01/20 1:08 am, Kuznetsov Sergei wrote:
> If I get you right, is this a problem with the web server.
>
Yes, exactly so.
> I tried to explain to them with about the same logic, but they could not
> reproduce the error and accordingly do not recognize the existence of
> the problem.
To reprod
On 21/01/20 9:09 pm, Alex Rousskov wrote:
On 1/20/20 11:28 PM, Amish wrote:
2) Is calling squidclient so frequently a right thing to do by netdata?
The answer depends on what cache manager query (or queries) your netdata
is sending to Squid. Sending some queries every second is perfectly
fine,
On 22/01/20 7:39 am, aashutosh kalyankar wrote:
> The problem I am seeing is the intercept port initiates HTTP connection
> to self-IP instead of the web server IP it gets from the DNS request.
Neither of those IPs should be used.
Self-IP indicates that the traffic is being delivered to the proxy
The problem I am seeing is the intercept port initiates HTTP connection to
self-IP instead of the web server IP it gets from the DNS request.
Filtered Tcpdump screenshot @
https://drive.google.com/open?id=0ByReiwdSAAY_VXBPTjF1M3dYTnBTTnhFVnRocXFveUlNSlNj
Server IP: Eth0: IP: 172.22.22.148/26 (Sam
On 1/21/20 6:54 AM, Amos Jeffries wrote:
> When the revalidation request is sent, the origin server updates the
> HTTP headers to say that the object is now 0 bytes in length:
>
> HTTP/1.1 304 Not Modified
> Server: nginx/1.4.6 (Ubuntu)
> Date: Tue, 21 Jan 2020 11:27:17 GMT
> Conte
On 1/20/20 11:28 PM, Amish wrote:
> 2) Is calling squidclient so frequently a right thing to do by netdata?
The answer depends on what cache manager query (or queries) your netdata
is sending to Squid. Sending some queries every second is perfectly
fine, but there are other, "heavy" queries that
Hi Amos,
That's right, it says that the resource cannot be cached.
Is that for you strict or can I enforce caching ?
Thanks,
Farid
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing l
On 21/01/20 10:36 pm, Kuznetsov Sergei wrote:
> Hello
>
> I run Squid 4.9 in non transparent mode with OPNsense (FreeBSD
> 11.2-RELEASE-p16-HBSD FreeBSD 11.2-RELEASE-p16-HBSD
> 87a7fc985c3(stable/19.7) amd64).
>
> Everything works except access to one website.
>
Which is broken. More on that
Hello
I run Squid 4.9 in non transparent mode with OPNsense (FreeBSD
11.2-RELEASE-p16-HBSD FreeBSD 11.2-RELEASE-p16-HBSD
87a7fc985c3(stable/19.7) amd64).
Everything works except access to one website.
Squid startup log is clean:
> 2020/01/21 13:56:43 kid1| Startup: Initializing Authenticatio
On 21.01.20 09:58, Amish wrote:
Recently, I started using netdata to monitor various system functions
(which also monitors squid)
I am using squid (v4.9) with transparent (NAT) as well as Proxy mode
(on different ports). Network has 10-15 users. Some on transparent
proxy (redirection to port
12 matches
Mail list logo
