Discussion on: What if I don't use GET (and DELETE)?

View post

Replies for: GET requests are cachable from the server. It helps to reduce the load on the server side. GET should be also only for a read action and not for ma...

Pacharapol Withayasakpunt • Dec 24 '20 • Edited

From what I have found,

Browser-side GET responses can be cached; but usually not other methods. However, GraphQL client (which uses POST) may cache the requests internally.
Server-side requests depend on the implementation.
- For Golang Gin that I am trying to use, maybe I cannot cache requests that aren't part of the URL. i.e. path, querystring (and is not limited to GET).

Also, regarding caching, what should I use for reading dynamic data? (that should not be cached, anyway)

mafflerbach • Dec 24 '20

Stil GET. Becaus it is documented in the rfc7231 to use GET for non manipulating request. The URL may is dynamic, but the response should be still the same if no other manipulating requests happen in between. And GET can also cashed on the server side or on a reverse proxy.

And in general a request body cannot cached.

Pacharapol Withayasakpunt • Dec 24 '20

but the response should be still the same if no other manipulating requests happen in between.

How would the caching engine know?

mafflerbach • Dec 24 '20

Well nothing is more complicated that cach invalidation...

But in short. You have multible 'cache header' posiblities from the client side. How vanish and other reverse proxies works - no detailed knowlage. But this seems a good explanation developer.mozilla.org/en-US/docs/W...