Allow for cacheTags to be passed on fetch requests (#247)

* Allow for cacheTags to be passed on `fetch` requests

Allowing cacheTags within the workers process to be processed as part of a standard fetch has been a highly requested feature. This new object within the request initialization will allow for supplemental Cache-Tag headers to be returned so that they can be stored with the relevant content. This will allow for better control over Purge by Tag mechanisms within the workers processes.

Implementation:

* Adds a new object to the `cf.d.ts` declaration.
* fixup! Allow for cacheTags to be passed on `fetch` requests

Co-authored-by: Mikey Sleevi <[email protected]>
Co-authored-by: Pete Bacon Darwin <[email protected]>

Author: 3 people

.changeset/rude-colts-help.md

@@ -0,0 +1,11 @@
+---
+"@cloudflare/workers-types": minor
+---
+
+Allow for cacheTags to be passed on fetch requests
+
+Allowing cacheTags within the workers process to be processed as part of a standard fetch has been a highly requested feature. This new object within the request initialization will allow for supplemental Cache-Tag headers to be returned so that they can be stored with the relevant content. This will allow for better control over Purge by Tag mechanisms within the workers processes.
+
+Implementation:
+
+- Adds a new object to the `cf.d.ts` declaration.

overrides/cf.d.ts

@@ -121,6 +121,15 @@ interface RequestInitCfProperties {
    * Only available for Enterprise customers.
    */
   cacheKey?: string;
+  /**
+   * This allows you to append additional Cache-Tag response headers
+   * to the origin response without modifications to the origin server.
+   * This will allow for greater control over the Purge by Cache Tag feature
+   * utilizing changes only in the Workers process.
+   *
+   * Only available for Enterprise customers.
+   */
+  cacheTags?: string[];
   /**
    * Force response to be cached for a given number of seconds. (e.g. 300)
    */