Search squid archive

Re: TCP_MISS only

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

 

Okay – but what happens if you are communicating with a non REST endpoint. Consider a Web services endpoint for example where a request is only interacted with via POST but the operation for example may frequently be a read based function akin to a HTTP GET? Is Squid just simply not going to help cache those requests? It is only helpful for more strict alignment to REST principles?

 

Kind regards,

Andy Armstrong 

安迪 阿姆斯特朗

Principal Specialist for Z Technologies

EMEA Squad Leader for Hybrid Cloud

Worldwide Community Leader for Hybrid Cloud

Member of the CTO Office Server & Storage EMEA

Distinguished Technical Specialist – The Open Group

IBM Master Inventor


Mobile: +447500103874

 

 

 

From: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> on behalf of Amos Jeffries <squid3@xxxxxxxxxxxxx>
Date: Tuesday, 27 September 2022 at 19:45
To: squid-users@xxxxxxxxxxxxxxxxxxxxx <squid-users@xxxxxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: TCP_MISS only

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 Return code so it sent 200 instead of 201, and
> the result is sadly the same, I get many, many lines like this:
>

Unfortunately that is not enough. POST method is also not cacheable by
default. See <https://www.rfc-editor.org/rfc/rfc9110#section-9.3.3 >

Consider what would happen when two clients POST different sets of data
to the same URL.  Which one should the cache handle *instead* of letting
it be delivered to a server?


> 1664272638.44310107 10.1.1.70 TCP_MISS/200 275 POST
> http://192.168.0.2:3001/InternalCommunicationServices/message/email   -
> HIER_DIRECT/192.168.0.2 application/json
>
> My suspicion is still that my refresh_pattern is wrong:
>
> refresh_pattern -i http://129.168.0.2:3001%5C/.*   10080 100% 43200
> override-lastmod
>

refresh_pattern directive does not make things cacheable when they are
not. It can only extend or shrink cacheability times.


HTH
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users 

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux