Thank you for this INFO
I use ufdbguard with the line
url_rewrite_program /usr/sbin/sgwrapper_ufdb
I had
redirect-https "https://www.jug in the config file for ufdbguard
Removing https:// from this definition removed the fake CONNECT https:443
entries
Anton Kornexl
-Ursprüngliche Na
On 1/16/20 3:39 PM, Kornexl, Anton wrote:
> Why are some https-requests logged with the correct hostname and no
> fake CONNECT https:443 and other requests are logged without correct
> domain but with fake CONNECT entries
For every specific log record, either there is a Squid bug or you are
deali
I use squid 4.9 on OpenSuse 15.1
Almost all https-Requests are logged with https:443
1579204357.578 1 1.2.3.4 NONE/503 0 CONNECT https:443 - HIER_NONE/- -
1579204358.623 0 1.2.3.4 NONE/503 0 CONNECT https:443 - HIER_NONE/- -
1579204358.672 1 1.2.3.4 NONE/503 0 CONNECT https:443 - H
On 17/01/20 3:08 am, Alex Rousskov wrote:
> On 1/16/20 3:06 AM, Kornexl, Anton wrote:
>> I see many requests with CONNECT https:443 in my access.log
>
>> How are these entries triggered?
>
> These records are logged when your Squid is done with an HTTP CONNECT
> tunnel or after Squid intercepts a
Alex, you are AWESOME!!
On Thu, 16 Jan 2020 at 17:11, Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 1/16/20 12:05 PM, robert k Wild wrote:
> > hi Alex,
> >
> > thanks for the notes
> >
> > so my child proxy, i have added -
> >
> > #forward clients IP
> > forwarded_
On 1/16/20 12:05 PM, robert k Wild wrote:
> hi Alex,
>
> thanks for the notes
>
> so my child proxy, i have added -
>
> #forward clients IP
> forwarded_for on
FYI: This is the default.
> and my parent -
>
> acl my_other_proxy srcdomain 10.110.130.80
If you identify your child proxy by its
hi Alex,
thanks for the notes
so my child proxy, i have added -
#forward clients IP
forwarded_for on
and my parent -
acl my_other_proxy srcdomain 10.110.130.80
follow_x_forwarded_for allow my_other_proxy
log_uses_indirect_client on
but in my parent logs, im still getting the ip of the child p
On 1/16/20 11:02 AM, Dieter Bloms wrote:
> Does anybody know how to enable wss support in squid, so the website can
> be reached even sslbump is enabled ?
If the service switches to websocket using an HTTP Upgrade mechanism,
then you need at least https://github.com/squid-cache/squid/pull/481
If
On 1/16/20 9:59 AM, robert k Wild wrote:
> i have two proxies (one sibling going to a parent)
FYI: "siblings" are proxies that fetch hits from each other. The proxy
"going to the parent" is usually called a "child" proxy:
clients -> child -> parent -> servers
> when i look at the parent pr
Hello,
I use squid 4.9 with enabled sslbump and it works great for the most
websites.
There are some websites, which use websockets like web.whatsapp.com
and can not be reached with enabled sslbump.
When I exclude this destination from sslbump, I get the qrcode, which
can be scanned with the smar
hi all,
i have two proxies (one sibling going to a parent)
when i look at the parent proxy access logs, it just logs the ip address of
the sibling proxy
if i add the lines below in my sibling proxy
acl localhost src 127.0.0.1
acl my_other_proxy srcdomain .proxy.example.com
follow_x_forwarded_fo
On 1/16/20 3:06 AM, Kornexl, Anton wrote:
> I see many requests with CONNECT https:443 in my access.log
> How are these entries triggered?
These records are logged when your Squid is done with an HTTP CONNECT
tunnel or after Squid intercepts a TLS connection. In very broad terms,
they are a sign
On 16.01.20 08:06, Kornexl, Anton wrote:
I see many requests with CONNECT https:443 in my access.log
How are these entries triggered?
They produce errors in some accounting scripts
what do you mean, triggered and what accounting scripts?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://
You can try policy based routing if DD-WRT supports that – see
https://docs.diladele.com/tutorials/policy_based_routing_squid/index.html
From: squid-users On Behalf Of
Robert Marshall
Sent: Thursday, 16 January 2020 09:30
To: squid-users@lists.squid-cache.org
Subject: [squid-users] Need help se
Hi all,
I'm trying to set up a transparent proxy on my network so that all devices
are forced to use Squid/SquidGuard for network traffic, and can filter out
undesirable destinations.
I have Squid/SquidGuard running on a Raspberry Pi 4, running the latest
release of Raspian Buster. The route is a
Hello
I see many requests with CONNECT https:443 in my access.log
How are these entries triggered?
They produce errors in some accounting scripts
Kind regards
Anton Kornexl
smime.p7s
Description: S/MIME cryptographic signature
___
16 matches
Mail list logo
