On 2023-10-30 13:08, ma...@web.de wrote:
Am 27.10.23 um 16:22 schrieb Alex Rousskov:
1. Enhance Squid to resolve transaction destination address once (on
first use/need). Remember/reuse resolved IP addresses. Log them via some
new %resolved_dst and %dst_resolution_detail codes.
This improvement
Am 27.10.23 um 16:22 schrieb Alex Rousskov:
On 2023-10-27 07:14, ma...@web.de wrote:
Am 26.10.23 um 21:11 schrieb Alex Rousskov:
On 2023-10-26 08:37, ma...@web.de wrote:
TL;DR: is there a way to get/log the resolved ip of a denied request?
TLDR: Bugs notwithstanding, use %
%
Sorry, my f
On 2023-10-27 07:14, ma...@web.de wrote:
Am 26.10.23 um 21:11 schrieb Alex Rousskov:
On 2023-10-26 08:37, ma...@web.de wrote:
TL;DR: is there a way to get/log the resolved ip of a denied request?
TLDR: Bugs notwithstanding, use %
%
Sorry, my first response was wrong: As you have correctly
Hi Alex,
Am 26.10.23 um 21:11 schrieb Alex Rousskov:
On 2023-10-26 08:37, ma...@web.de wrote:
TL;DR: is there a way to get/log the resolved ip of a denied request?
TLDR: Bugs notwithstanding, use %
%http://127.0.0.1:3128 https_proxy=http://127.0.0.1:3128 wget
http://www.example.org
--2023-
On 2023-10-26 08:37, ma...@web.de wrote:
TL;DR: is there a way to get/log the resolved ip of a denied request?
TLDR: Bugs notwithstanding, use %
We have a rather large ip based malware blacklist (dst acl) and
sometimes a destination is blocked inadvertantly because of a false
positive entry in
Hi list,
TL;DR: is there a way to get/log the resolved ip of a denied request?
We have a rather large ip based malware blacklist (dst acl) and
sometimes a destination is blocked inadvertantly because of a false
positive entry in this list.
This happens most often with CDNs where the ips of a de
