research: the hedex content API, its two ids, and the retired host that used to serve it (#807) #1893

Merged
jaylouisw merged 1 commit from catalogue/1117-2025 into main 2026-11-17 20:41:00 +00:00
Owner

Refs #807 - records evidence, does not close the issue.

What is new. The hedex viewer is a shell that loads one bundle, /hedex/lst/js/index-legacy-DaAKRolI.js (200, 361,996 B). That bundle names the content endpoints and their template: /hedex/api/pages/${docId}/${topicLibId}/${topicLibVer}/${topicUrl} (its own RegExp is /hedex/api/pages/[^/]+/([^/]+)/([^/]+)/([^#?]+)), plus /hedex/api/navi/ and /hedex/api/search/. Earlier passes had the document id only; the 302 from any /hedex/pages/... URL hands back the missing pair in its Location header (tocLibId=BEJ09047&tocLibVer=03 for the OSN 9800 set).

What the API answers (crawler UA, 2026-11-17):

  • /hedex/api/pages/EDOC1100126589/BEJ09047/03/resources/help/wdm/9800/hd/line/n210/n210.html -> 404, 18 B, No doc data found. (same without .html)
  • /hedex/api/navi/EDOC1100126589/first-level-tree -> 404, {"status":404,"message":"No doc data found.","data":null}
  • https://support.huawei.cn/hedex/api/pages/EDOC1100625542/BEJ09047/03/resources/help -> 401, NOT LOGIN!
  • https://support.huawei.cn/enterprise/en/doc/EDOC1100163901 -> 302 -> view/notFound, 404, 452,479 B

So the wall is per-document (404 = not served, 401 = needs a session), the .cn mirror repeats it byte-for-byte, and no first-level-tree/topic call will disclose a lib/ver pair to a caller without a session.

The one host that used to leak it is retired. info.support.huawei.com still appears in search as an openly readable hedex content host (.../hedex/api/pages/EDOC1000163559/YEI0812D/19/resources/en-us_topic_0000001238552187.html, and the pt/br/fr E9605 product pages), but every path now answers 302 -> https://support.huawei.com/supportindex/ (200, 91,294 B). Wayback has no capture of .../hedex/api/pages/EDOC1100625542 or .../EDOC1100163901 (CDX prefix query: 200, 0 bytes), while the host itself is archived from 2021-02-18 on.

Not an access gap in the ordinary sense. e-file.huawei.com/.../OptiXtrans%20E9600%20TNG2SRAPXF.pdf fetched today: 200, application/pdf, 1,104,102 B, pdftotext -layout prints section 1.9 Valid Slots for E9605/E9612/E9624/E9624X. Same family, same server, anonymous - so a published client-board chapter would be reachable; the TNG1N* ones are simply not published.

Gates: node scripts/syntax-check.js (393 files, all OK), node scripts/audit-port-types.js (no port contradicts its declared type), node scripts/check-canonical-urls.js (3071 files OK). No spec touched, so no importer/catalogue change.

Spec path: research/optixtrans-hedex-content-api.md.

Refs #807 - records evidence, does not close the issue. **What is new.** The hedex viewer is a shell that loads one bundle, `/hedex/lst/js/index-legacy-DaAKRolI.js` (200, 361,996 B). That bundle names the content endpoints and their template: `/hedex/api/pages/${docId}/${topicLibId}/${topicLibVer}/${topicUrl}` (its own RegExp is `/hedex/api/pages/[^/]+/([^/]+)/([^/]+)/([^#?]+)`), plus `/hedex/api/navi/` and `/hedex/api/search/`. Earlier passes had the document id only; the `302` from any `/hedex/pages/...` URL hands back the missing pair in its `Location` header (`tocLibId=BEJ09047&tocLibVer=03` for the OSN 9800 set). **What the API answers** (crawler UA, 2026-11-17): - `/hedex/api/pages/EDOC1100126589/BEJ09047/03/resources/help/wdm/9800/hd/line/n210/n210.html` -> 404, 18 B, `No doc data found.` (same without `.html`) - `/hedex/api/navi/EDOC1100126589/first-level-tree` -> 404, `{"status":404,"message":"No doc data found.","data":null}` - `https://support.huawei.cn/hedex/api/pages/EDOC1100625542/BEJ09047/03/resources/help` -> 401, `NOT LOGIN!` - `https://support.huawei.cn/enterprise/en/doc/EDOC1100163901` -> 302 -> `view/notFound`, 404, 452,479 B So the wall is per-document (404 = not served, 401 = needs a session), the `.cn` mirror repeats it byte-for-byte, and no `first-level-tree`/`topic` call will disclose a lib/ver pair to a caller without a session. **The one host that used to leak it is retired.** `info.support.huawei.com` still appears in search as an openly readable hedex content host (`.../hedex/api/pages/EDOC1000163559/YEI0812D/19/resources/en-us_topic_0000001238552187.html`, and the `pt`/`br`/`fr` E9605 product pages), but every path now answers 302 -> `https://support.huawei.com/supportindex/` (200, 91,294 B). Wayback has no capture of `.../hedex/api/pages/EDOC1100625542` or `.../EDOC1100163901` (CDX prefix query: 200, 0 bytes), while the host itself is archived from 2021-02-18 on. **Not an access gap in the ordinary sense.** `e-file.huawei.com/.../OptiXtrans%20E9600%20TNG2SRAPXF.pdf` fetched today: 200, `application/pdf`, 1,104,102 B, `pdftotext -layout` prints section 1.9 Valid Slots for E9605/E9612/E9624/E9624X. Same family, same server, anonymous - so a published client-board chapter would be reachable; the `TNG1N*` ones are simply not published. Gates: `node scripts/syntax-check.js` (393 files, all OK), `node scripts/audit-port-types.js` (no port contradicts its declared type), `node scripts/check-canonical-urls.js` (3071 files OK). No spec touched, so no importer/catalogue change. Spec path: `research/optixtrans-hedex-content-api.md`.
research: the hedex content API, its two ids, and the retired host that used to serve it (#807)
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 6s
ee566ed131
The hedex viewer's own bundle names the content endpoints (/hedex/api/pages/<docId>/<topicLibId>/<topicLibVer>/<topicUrl>) and the 302 from any /hedex/pages/... URL hands back the libId/libVer pair earlier probes lacked. Called with those ids the API answers 404 "No doc data found" for the OSN 9800 n210 chapter and for E9600 V100R026C00, and 401 NOT LOGIN for EDOC1100625542 - so the wall is per-document, not uniform, and still closed. info.support.huawei.com, the one host that used to serve chapter text anonymously and is still indexed that way, now 302s every path to supportindex; Wayback holds no capture of either board-datasheet document id. Chapter PDFs are otherwise fetchable when published (TNG2SRAPXF, 1,104,102 B, Valid Slots table read today), so the client-board chapter is unpublished, not unreachable. No spec added; #803/#807/#808/#810 stay open.
jaylouisw force-pushed catalogue/1117-2025 from ee566ed131
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 6s
to 05af0f110f
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Classify the change (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 12s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 20s
2026-11-17 20:36:52 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1893
No description provided.