You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: files/en-us/web/http/reference/headers/etag/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ The HTTP **`ETag`** (entity tag) {{Glossary("response header")}} is an identifie
11
11
It lets [caches](/en-US/docs/Web/HTTP/Guides/Caching) be more efficient and save bandwidth, as a web server does not need to resend a full response if the content has not changed.
12
12
Additionally, ETags help to prevent simultaneous updates of a resource from overwriting each other (["mid-air collisions"](#avoiding_mid-air_collisions)).
13
13
14
-
If the resource at a given URL changes, a new `Etag` value _must_ be generated.
14
+
If the resource at a given URL changes, a new `ETag` value _must_ be generated.
15
15
A comparison of them can determine whether two representations of a resource are the same.
16
16
17
17
<tableclass="properties">
@@ -59,7 +59,7 @@ ETag: W/"0815"
59
59
60
60
With the help of the `ETag` and the {{HTTPHeader("If-Match")}} headers, you can detect mid-air edit collisions (conflicts).
61
61
62
-
For example, when editing a wiki, the current wiki content may be hashed and put into an `Etag` header in the response:
62
+
For example, when editing a wiki, the current wiki content may be hashed and put into an `ETag` header in the response:
0 commit comments