https://cloud.google.com/apis/design/design_patterns#etags According to this page: To support ETags, an API should include a string field etag in the resource definition.
I want to know why Google suggest us include the etag in response body, but not in response header???
As I learnt from this https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching#validating_cached_responses_with_etags
Browser will automatically handle the etag if we put it in header, so why we want to put it in body?
Aucun commentaire:
Enregistrer un commentaire