Javi Velasco 82adaee0cd Allow to opt-out from preflight cache (#32767) ... Fixes #32727 With this PR we introduce a new header that can be used to respond from Middleware `x-middleware-cache`. When the value of this header is set to `no-cache`, the client will **not** store the effects read from a preflight response to be used in an upcoming check. Instead of using `Cache-Control` we are using a custom header to not mess with browser specific caching. Accepting a specific value to opt out (`no-cache`) opens the future opportunity of having other caching strategies. This feature solves the issue of having a preflight request whose parameters can change from the client affecting the effects. For example, having a cookie that would make a middleware rewrite to one pathname or another and allowing to change that cookie from the client. In that case we'd always need to revalidate the effects on navigation synchronously. Of course when using this feature it is possible that we add some latency on navigation so the preferred mechanism will be caching by default since it covers the most common use cases.		2022-01-03 18:13:28 +00:00
..
utils	Fix issue with escape-string-regexp in IE11 (#32708)	2022-01-03 11:41:50 -06:00
router.ts	Allow to opt-out from preflight cache (#32767)	2022-01-03 18:13:28 +00:00