TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Fixes for the strong & weak ETags guide [ci skip]

Browse Source
This commit is contained in:
Roque Pinel 2016-04-07 23:16:12 -04:00
parent ee96c8fff4
commit e08232cda2
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
guides/source/caching_with_rails.md
View File

@ -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.