Skip to content

Commit 4016808

Browse files
committed
fix(edge): own section
1 parent acc39ad commit 4016808

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

network/edge-services/how-to/configure-cache.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,15 +88,15 @@ This allows you to specify the precise objects that you want to clear from the c
8888

8989
The specified objects are purged from your cache and you are returned to the Edge Services dashboard.
9090

91-
<Message type="tip">
92-
To avoid repeated purging, you can also set the `Cache-Control` HTTP header directly on your files/objects. This allows you to define how long items should remain in the cache before being freshly retrieved from the origin.
91+
## How to use Cache-Control
9392

94-
For Object Storage bucket origins, the following example call to the S3 API updates the `Cache-Control` header for **all** objects in the bucket, setting a maximum age of 60 seconds before they must be freshly retrieved. Edge Services will respect this header when determining from where to fetch content.
93+
To avoid repeated purging, you can also set the `Cache-Control` HTTP header directly on your files/objects. This allows you to define how long items should remain in the cache before being freshly retrieved from the origin. Edge Services will respect this header when determining from where to fetch content.
94+
95+
For Object Storage bucket origins, the following example call to the S3 API updates the `Cache-Control` header for **all** objects in the bucket, setting a maximum age of 60 seconds before they must be freshly retrieved.
9596

9697
```
9798
./s3cmd --recursive modify --add-header="Cache-Control:max-age=60" s3://yourbucket/
9899
```
99-
</Message>
100100

101101
## How to disable your cache
102102

0 commit comments

Comments
 (0)