Skip to content

Commit b822d24

Browse files
Merge pull request #280736 from Harikrishnan-M-B/patch-17
Update cdn-how-caching-works.md
2 parents a764f01 + ca18fbe commit b822d24

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/cdn/cdn-how-caching-works.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,9 @@ Not all resources can be cached. The following table shows what resources can be
109109

110110
For **Azure CDN Standard from Microsoft** caching to work on a resource, the origin server must support any HEAD and GET HTTP requests and the content-length values must be the same for any HEAD and GET HTTP responses for the asset. For a HEAD request, the origin server must support the HEAD request, and must respond with the same headers as if it received a GET request.
111111

112+
> [!NOTE]
113+
> Requests that include authorization header will not be cached.
114+
112115
## Default caching behavior
113116

114117
The following table describes the default caching behavior for the Azure Content Delivery Network products and their optimizations.

0 commit comments

Comments
 (0)