Well, the ready to use products are not always what you need or want.
Even squid is not good enough for many scenarios...
If it works with shallalist it's nice but not the real deal for most cases.
Vieri might or might not clarify his scenario, but the issue here is not other
then working with sq
It is just enough not to reinvent the wheel. What needs op - already
exists and is called ufdbguard. And it's works perfectly with shallalist :)
13.09.2017 2:51, Eliezer Croitoru пишет:
> I just must add that if you understand how TCP works(which the helpers use to
> communicate with squid) then
I just must add that if you understand how TCP works(which the helpers use to
communicate with squid) then it makes sense that it is possible that...
The sender (ie squid) sent 100 lines but the client software yet to process
them since it's in the OS or other software\hardware related buffer.
F
On 13/09/17 00:01, Garbacik, Joe wrote:
I am using an alternate filename for my squid configuration and am
trying to validate the file below going live with it. Should I be able
to use both the –k parse and the –f filename options at the same time?
Yes.
It looks like “-k parse” is defaulting
On 12/09/17 22:59, Vieri wrote:
From: Amos Jeffries
That is all it needs to do to begin with; parse off the numeric value
from the input line and send it back as prefix on the output line. The
helper does not need threading or anything particularly special
I am using an alternate filename for my squid configuration and am trying to
validate the file below going live with it. Should I be able to use both the –k
parse and the –f filename options at the same time? It looks like “-k parse” is
defaulting to only use only /etc/squid/squid.conf.
# squid
From: Amos Jeffries
>
> That is all it needs to do to begin with; parse off the numeric value
> from the input line and send it back as prefix on the output line. The
> helper does not need threading or anything particularly special for the >
> minimal support
