How to invalidate 'other' URIs in case of a PUT request?

Change the ETag returned by the other two URLs to a new value (eg, a hash of the data).

Let me rephrase my problem. The client has already invoked the 3 URLs before it made the update. So it already has the representations of the resource.

Let's say that the expires header was set on those representations to be in an hour from now. After the update was made, the other two resources should have been stale immediately. But the client will not know that unless it makes a GET on them, which won't happen for an hour.

– Sam Aug 29 at 2:20 1 You can't tell the client to invalidate something without making a request, unless you build an invalidate command into your protocol. – SLaks Aug 29 at 2:23 Care to elaborate? What do you mean by invalidate command?

– Sam Aug 29 at 5:48 Add some command to the response (perhaps a custom header) that tells the client to invalidate a specific URL. HTTP does not have such a command, so you'd need to make one yourself. – SLaks Aug 29 at 12:17.

Lname=Doe redirect to /person/1234 instead of returning the entity data themselves.

Alternatively, return a Content-Location: /person/1234 header for requests to the two URIs /person/list?.... That will tell any cache that it should consider any copies of such responses as stale. Ietf. Org/id/draft-ietf-httpbis-p6-cache-16.

Txt (Section 2.5) – Jan Algermissen Aug 30 at 10:31.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.