On 23/10/24 01:34, Piana, Josh wrote:
Amos,
Thank you for the update in regards to the credentials.
I looked into it a bit more to and it helped clear my misunderstanding.
The credentialstls configuration directive only controls how often these credentials are
internally verified by Squid. It
auth_param basic keep_alive on
auth_param basic credentialsttl 2 hours
auth_param basic realm
-Original Message-
From: squid-users On Behalf Of Amos
Jeffries
Sent: Tuesday, October 22, 2024 6:05 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a d
On 19/10/24 08:52, Piana, Josh wrote:
On a separate note, what would cause me to need to authenticate everytime I
open a new browser? My credentials are supposed to last a week.
HTTP requires every request to be authenticated.
I assume you mean a popup appears? that would be a Browser decis
proxy_auth REQUIRED
#
-Original Message-
From: squid-users On Behalf Of
Matus UHLAR - fantomas
Sent: Friday, October 18, 2024 3:34 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of
On 17.10.24 20:40, Piana, Josh wrote:
To clarify on the test, port 4434 is the port that was assigned to get
access to that device, one of our firewalls.
I looked at the old Squid config that we have, and it seems this was setup
in a way that internal networks were not being passed through the
esday, October 16, 2024 11:45 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click links or
open attachments unless you recognize the sender and know the content is safe.
O
: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click links or
open attachments unless you recognize the sender and know the content is safe.
On 16/10/24 09:39, Piana, Josh wrote:
>
On 16.10.24 20:03, Piana, Josh wrote:
We do have a firewall in front of the Squid server.
We're using a Checkpoint firewall but I've been told, a few times, that the
firewall is not blocking traffic coming from the proxy.
I guess that the whole problem lies in your network.
172.27.46.253 is
On 16/10/24 09:39, Piana, Josh wrote:
Amos,
Thank you for getting back to me and clarifying.
I ran this command:
#wget -Y off 172.27.46.253
Response:
--2024-10-15 16:36:15-- http://172.27.46.253/
Connecting to 172.27.46.253:80... connected.
HTTP request sent, awaiting response... 301 Moved Pe
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click links or
open attachments unless you recognize the sender and know the content is safe.
On 16.10.24 16:10, Piana, Josh wrote:
>After running the below
On 16.10.24 16:10, Piana, Josh wrote:
After running the below commands, I did restart squid and tested again. No luck.
Here's the outputs:
# iptables -L -n -v
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
# i
, 2024 10:22 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click links or
open attachments unless you recognize the sender and know the content is safe.
On 16.10.24 13:43, P
riginal Message-
From: squid-users On Behalf Of
Matus UHLAR - fantomas
Sent: Wednesday, October 16, 2024 7:56 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click l
ssage-
From: squid-users On Behalf Of
Matus UHLAR - fantomas
Sent: Wednesday, October 16, 2024 7:56 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click links or
open att
rules to that network?
-Original Message-
From: squid-users On
Behalf Of Matus UHLAR - fantomas
Sent: Thursday, October 10, 2024 3:21 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexce
e here if applicable.
-Original Message-
From: squid-users On Behalf Of Amos
Jeffries
Sent: Thursday, October 10, 2024 9:25 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. D
n Behalf Of
Matus UHLAR - fantomas
Sent: Thursday, October 10, 2024 3:21 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click links or
open attachments unless you recognize the sen
HLAR - fantomas
Sent: Thursday, October 10, 2024 3:21 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Unable to access a device over port 4434
Caution: This email originated from outside of Hexcel. Do not click links or
open attachments unless you recognize the sender and
On 09.10.24 19:59, Piana, Josh wrote:
I'm running into an issue wherein, when using Squid proxy, I'm unable to get to
one of our management devices from port 4434.
I've already verified that this device is not blocking access from the proxy
directly, and should be allowed to get to the access
Hello Squid users,
I'm running into an issue wherein, when using Squid proxy, I'm unable to get to
one of our management devices from port 4434.
I've already verified that this device is not blocking access from the proxy
directly, and should be allowed to get to the access page.
- Wh
20 matches
Mail list logo
