@anchrd/intel-api 0.26.0 → 0.27.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/build/build.js +10 -1
- package/package.json +2 -2
package/dist/build/build.js
CHANGED
|
@@ -18,11 +18,20 @@ const defaultLogo = `export const customLogoUrl: string | null = null;\n`;
|
|
|
18
18
|
//
|
|
19
19
|
// Without it every asset answers with the platform default `public, max-age=0, must-revalidate`,
|
|
20
20
|
// and `public` lets a browser store an ERROR answer too. A `403` that appears once during setup is
|
|
21
|
-
// then replayed on
|
|
21
|
+
// then replayed on BACK/FORWARD WITHOUT a request leaving the browser — invisible in the worker
|
|
22
22
|
// log, in the Cloudflare Access log, in the firewall and in Cloudflare Analytics, while `curl`
|
|
23
23
|
// against the same address keeps answering `200`. The second rule matters more here than in Gate:
|
|
24
24
|
// the UI ships 1.9 MB of fingerprinted assets that are revalidated on every navigation today.
|
|
25
25
|
//
|
|
26
|
+
// ⚠️ The ERROR answer is NOT replayed on every navigation — that is the asset line right above, a
|
|
27
|
+
// different statement about `/assets/*`, and it stays as it is. The narrower shape is what makes
|
|
28
|
+
// this expensive to diagnose: `must-revalidate` DOES hold for a fresh navigation, so retyping the
|
|
29
|
+
// address returns the REPAIRED page (`200 /` in the worker log), while a history navigation replays
|
|
30
|
+
// the stored answer without any freshness check (`transferSize: 0`). Measured in Chromium with a
|
|
31
|
+
// real cache, anchrd/gate#399. Whoever retypes the address rules the browser cache out and loses
|
|
32
|
+
// the afternoon of anchrd/gate#329 a second time — going BACK is the only handle that shows the
|
|
33
|
+
// frozen answer.
|
|
34
|
+
//
|
|
26
35
|
// ⚠️ `! Cache-Control` is not decoration, and the naive two-rule form from the ticket is WRONG.
|
|
27
36
|
// A request matching several rules inherits ALL their headers, and a header named twice is joined
|
|
28
37
|
// with a comma. Measured against `wrangler dev` 4.112.0 with both spellings side by side:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@anchrd/intel-api",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.27.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "UNLICENSED",
|
|
6
6
|
"repository": {
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"typecheck": "tsc --noEmit"
|
|
43
43
|
},
|
|
44
44
|
"dependencies": {
|
|
45
|
-
"@anchrd/gate-sdk": "^0.
|
|
45
|
+
"@anchrd/gate-sdk": "^0.21.0",
|
|
46
46
|
"@anchrd/intel-contract": "^0.22.0",
|
|
47
47
|
"@cfworker/json-schema": "^4.1.1",
|
|
48
48
|
"@modelcontextprotocol/sdk": "^1.30.0",
|