Remove HEAD request method limitation from On-Demand ISR example (#369)

vercel · Jul 26, 2022 · f74ccc9 · f74ccc9 · vercel · Jul 26, 2022
1 parent a48b287
commit f74ccc9
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/build-output-api/on-demand-isr/.vercel/output/functions/revalidate.func/index.js b/build-output-api/on-demand-isr/.vercel/output/functions/revalidate.func/index.js
@@ -15,7 +15,7 @@ function revalidate(host, path) {
       hostname: host,
       port: 443,
       path,
-      method: 'GET', // MUST be "GET" ("HEAD" and "POST" methods will not work)
+      method: 'GET', // MUST be "GET" or "HEAD" ("POST" method will not work)
       headers: {
         'x-prerender-revalidate': bypassToken
       }

diff --git a/build-output-api/on-demand-isr/README.md b/build-output-api/on-demand-isr/README.md
@@ -18,7 +18,7 @@ Click on one of the "Revalidate" links to see the associated value update. After
 
 When using Prerender Functions, you may want to revalidate the cache for a specific path based on an event (On-Demand).
 
-To revalidate a path to a Prerender Function, make a `GET` request to that path with a header of `x-prerender-revalidate: <bypassToken>`. The `<bypassToken>` must match the value in that Prerender Function's `<name>.prerender-config.json` file.
+To revalidate a path to a Prerender Function, make a `GET` or `HEAD` request to that path with a header of `x-prerender-revalidate: <bypassToken>`. The `<bypassToken>` must match the value in that Prerender Function's `<name>.prerender-config.json` file.
 
 In this demo, you can see this happening with two paths: `/` and `/data`.