fix: don't use stale-while-revalidate for loaders

the browser doesn't have a way to notify you when it updated.

Author: wmertens

packages/qwik-router/src/middleware/request-handler/handlers/loader-handler.ts

@@ -108,7 +108,6 @@ export function loaderHandler(routeLoaders: LoaderInternal[]): RequestHandler {
     // Set cache headers - aggressive for loaders
     requestEv.cacheControl({
       maxAge: 300, // 5 minutes
-      staleWhileRevalidate: 3600, // 1 hour
     });
 
     const data = await _serialize([loaders[loaderId]]);

packages/qwik-router/src/middleware/request-handler/handlers/qdata-handler.ts

@@ -32,8 +32,7 @@ export async function qDataHandler(requestEv: RequestEvent) {
 
   // Set cache headers
   requestEv.cacheControl({
-    maxAge: 300, // 5 minutes
-    staleWhileRevalidate: 3600, // 1 hour
+    maxAge: 60, // 1 minute
   });
 
   // write just the page json data to the response body

packages/qwik-router/src/middleware/request-handler/types.ts

@@ -399,6 +399,10 @@ export interface CacheControlOptions {
   /**
    * The stale-while-revalidate response directive indicates that the cache could reuse a stale
    * response while it revalidates it to a cache.
+   *
+   * Note: there is no mechanism that updates the application when the revalidation happens. Use
+   * this only when you know you will be fetching the revalidated resource again in the very near
+   * future.
    */
   staleWhileRevalidate?: number;