On 22/10/22 01:50, Andy Armstrong wrote:
Hi Amos, All,
I continue to struggle with only receiving TCP_MISS when using
squid-cache. I have now implemented a server which is responding to HTTP
GETs. I have checked the endpoint with redbot.org and it states that :
1/The response allows all
Andy
Armstrong
Date: Thursday, 29 September 2022 at 15:00
To: Amos Jeffries , squid-users@lists.squid-cache.org
Subject: [EXTERNAL] Re: [squid-users] TCP_MISS only
Hi, Excellent I understand and agree with what you are saying. Is this
behaviour documented within the Squid documentation anyw
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
list – The Open Group
IBM Master Inventor
Mobile: +447500103874
From: squid-users on behalf of Amos
Jeffries
Date: Thursday, 29 September 2022 at 13:06
To: squid-users@lists.squid-cache.org
Subject: [EXTERNAL] Re: [squid-users] TCP_MISS only
On 28/09/22 07:56, Andy Armstrong wrote:
&g
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
rage EMEA
Distinguished Technical Specialist – The Open Group
IBM Master Inventor
Mobile: +447500103874
From: squid-users on behalf of Amos
Jeffries
Date: Tuesday, 27 September 2022 at 19:45
To: squid-users@lists.squid-cache.org
Subject: [EXTERNAL] Re: [squid-users] TCP_MISS only
On 27/09/22 2
On 27/09/22 23:01, Andy Armstrong wrote:
Hi Alex,
That makes a lot of sense, I don’t know how I overlooked that – thank
you. I also agree, logically caching a 201 response makes little sense,
and it was just an example I had that was easy to try so I used that.
I just altered the HTTP
shed Technical Specialist – The Open Group
IBM Master Inventor
Mobile: +447500103874
From: squid-users on behalf of Alex
Rousskov
Date: Monday, 26 September 2022 at 21:07
To: squid-users@lists.squid-cache.org
Subject: [EXTERNAL] Re: [squid-users] TCP_MISS only
On 9/26/22 15:27, Andy Armstrong w
On 9/26/22 15:27, Andy Armstrong wrote:
My aim – is that for any HTTP response from 192.168.0.2:3001 is
cached and served from the cache.
1664219486.83610098 10.1.1.70 TCP_MISS/201 492 POST
http://192.168.0.2:3001/InternalCommunicationServices/message/email -
HIER_DIRECT/192.168.0.2
Hi all,
I am trying to use Squid Cache for the first time. My aim – is that for any
HTTP response from 192.168.0.2:3001 is cached and served from the cache.
My config is as follows:
http_port 3128
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src
10 matches
Mail list logo
