research: the hedex content API, its two ids, and the retired host that used to serve it (#807) #1893
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1893
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1117-2025"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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; the302from any/hedex/pages/...URL hands back the missing pair in itsLocationheader (tocLibId=BEJ09047&tocLibVer=03for 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 BSo the wall is per-document (404 = not served, 401 = needs a session), the
.cnmirror repeats it byte-for-byte, and nofirst-level-tree/topiccall 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.comstill appears in search as an openly readable hedex content host (.../hedex/api/pages/EDOC1000163559/YEI0812D/19/resources/en-us_topic_0000001238552187.html, and thept/br/frE9605 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/EDOC1100625542or.../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.pdffetched today: 200,application/pdf, 1,104,102 B,pdftotext -layoutprints section 1.9 Valid Slots for E9605/E9612/E9624/E9624X. Same family, same server, anonymous - so a published client-board chapter would be reachable; theTNG1N*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.ee566ed13105af0f110f