I know you can map a username to a parent proxy (i.e. cache_peer) using and acl
directive, e.g.
```
acl parent_proxy_testuser_1 proxy_auth testuser1
cache_peer parent 0 proxy-only
cache_peer_access parent1 allow parent_proxy_testuser_1
cache_peer_access parent1 deny !parent_proxy_testuser_1
```
On Tuesday 22 September 2020 at 22:35:36, Ajb B wrote:
> how can you map the user password to a parent proxy?
>
> so that
>
> testuser1:qvmgPUJ5xW-121@18.234.74.214:3292
> testuser1:qvmgPUJ5xW-122@18.234.74.214:3292
> testuser1:qvmgPUJ5xW-123@18.234.74.214:3292
> map to a different parent proxy?
> > 2020/09/22 09:34:07| FATAL: check failed: opening()
> > exception location: tunnel.cc(1305) noteDestinationsEnd
> > current master transaction: master359979
>
> This is still bug #5055. I hope we will post an official pull request
> properly addressing it soon.
I can easily test it he
On 9/22/20 3:47 AM, Ralf Hildebrandt wrote:
> I'm getting (with the same hand-build squid versions!) a LOT
> (about once every 15 Minutes) of crashes like this one:
>
> 2020/09/22 09:34:07| FATAL: check failed: opening()
> exception location: tunnel.cc(1305) noteDestinationsEnd
> current m
* Ralf Hildebrandt :
> 2020/09/22 09:34:07| FATAL: check failed: opening()
> exception location: tunnel.cc(1305) noteDestinationsEnd
> current master transaction: master359979
I had to go back as far as 5.0.2 to exclude master commit 25b0ce4, now
it's stable (running for an hour without a
I've been running squid-5 and squid-6 (both release and HEAD) on my
old proxy farm. Four machines, ubuntu bionic. All was well, except for
the occasional crash.
I filed bug reports, and the preliminary patches helped with the
crashes:
https://bugs.squid-cache.org/show_bug.cgi?id=5055
https://bugs
