From e08232cda2efd8c25e1fb08fe7d44915a64f5106 Mon Sep 17 00:00:00 2001 From: Roque Pinel Date: Thu, 7 Apr 2016 23:16:12 -0400 Subject: Fixes for the strong & weak ETags guide [ci skip] --- guides/source/caching_with_rails.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'guides/source') diff --git a/guides/source/caching_with_rails.md b/guides/source/caching_with_rails.md index ae204a55d6..745f09f523 100644 --- a/guides/source/caching_with_rails.md +++ b/guides/source/caching_with_rails.md @@ -526,7 +526,7 @@ Weak ETags have a leading `W/` to differentiate them from strong ETags. "618bbc92e2d35ea1945008b42799b0e7" → Strong ETag ``` -Unlike weak ETag, Strong ETag implies that response should be exactly same +Unlike weak ETag, strong ETag implies that response should be exactly the same and byte by byte identical. Useful when doing Range requests within a large video or PDF file. Some CDNs support only strong ETags, like Akamai. If you absolutely need to generate a strong ETag, it can be done as follows. -- cgit v1.2.3