On 3/27/19 5:29 PM, Yanier Salazar Sanchez wrote:
> I have squid4.4 installed in linux on ubuntu 18.04.1 and [...]
> delay_pools are functioning as if they didn’t have speed limits
While testing peering support for SslBump transactions[1], Factory has
discovered that delay pools are broken in
Good afternoon:
I have squid4.4 installed in linux on ubuntu 18.04.1 and I have the
following problem with the delay_pools aren't working properly, the squid
identify them with their number but do not comply with the speed limits
They are functioning as if they didn't have speed limits
Someone has
On 3/27/19 3:17 PM, sq...@buglecreek.com wrote:
> Operating in reverse proxy mode. I'm trying to send a TCP reset in response
> to the acl below:
>
> acl example_url url_regex -i [^:]+://[^0-9]*.example.com.*
> deny_info TCP_RESET example_url
> http_access deny example_url
>
> Looking at the
Operating in reverse proxy mode. I'm trying to send a TCP reset in response
to the acl below:
acl example_url url_regex -i [^:]+://[^0-9]*.example.com.*
deny_info TCP_RESET example_url
http_access deny example_url
Looking at the packets I see the following response:
HTTP/1.0 403 Forbidden
What about some sort of netflow service?
In the ISP world the radius server does accounting and it's a bit different
ntop have a network probe that might help you:
https://www.ntop.org/
I am using routers to do this kind of a task instead of the proxy.
The other option is to use QOS between the
