From: K R, Bharath
Sent: Thursday, September 29, 2022 10:31 PM
To: squid-users@lists.squid-cache.org
Cc: Kasat, Puneeth Kumar ; Boddupalli, Vikram
; Uppal, Tanjot Singh
Subject: NTLM V2 Set up for Squid issue
Hi Team,
We see the below error while configuring Squid for NTLM V2.
1664469456.486
On 30/09/22 03:45, Majed Zouhairy wrote:
Peace, does squid still not support long urls?
Squid supports long URLs. If it did not those log entries would be
shorter and indicate clients being rejected with "414 URI Too Long".
Your problem is the length of the log line. The logging modules
On 30/09/22 02:59, Andy Armstrong wrote:
Hi,
Excellent I understand and agree with what you are saying. Is this
behaviour documented within the Squid documentation anywhere, or is this
more ‘how does the HTTP specification handle caching’?
It is HTTP basics. I have just re-phrased details
Peace, does squid still not support long urls?
sudo sarg -x -z
SARG: Init
SARG: Loading configuration file "/usr/share/sarg/sarg.conf"
SARG: TAG: access_log /var/log/squid/access.log
SARG: TAG: title "Squid User Access Reports"
SARG: TAG: font_face Tahoma,Verdana,Arial
SARG: TAG: font_size 18px
Hi,
Excellent I understand and agree with what you are saying. Is this behaviour
documented within the Squid documentation anywhere, or is this more ‘how does
the HTTP specification handle caching’?
I am moving forward with a HTTP GET to see if that works per my use case. I
assume therefore
On 27/09/22 02:25, Alex Rousskov wrote:
On 9/26/22 05:51, Théo BARRAGUE wrote:
entry is null so peerGetSomeNeighbor is never called
I did not check all the details, but it looks like Squid ICMP code
(ab)uses StoreEntry-linked metadata. Basic CONNECT tunnels lack
StoreEntry because they
On 28/09/22 23:11, Punyasloka Arya wrote:
We have our squid 3.5 proxy running on centos 6 for 500 users
Desktop video conference application Microsoft Team Meetings sessions and
other VC apps often get disconnected. Audio goes off and reconnects
automatically.
At the same time browsing and other
On 28/09/22 07:56, Andy Armstrong wrote:
Okay – but what happens if you are communicating with a non REST
endpoint.
You are still communicating over HTTP. To interact with and benefit from
HTTP agents like caches you need to comply to the HTTP semantics they use.
IMO, REST is just a useful
