research(oceanprotect): a rendered section and a missing one both answer 200 + shell - control the user-agent (#743) #1867

Merged
jaylouisw merged 1 commit from catalogue/1117-1555 into main 2026-11-17 16:06:13 +00:00
Owner

Does not close #743 - the IOM census is still unpublished, and no spec is written from research notes.

What this pass found

1. The probe method was under-controlled. The support doc viewer returns the same 3,800-byte SPA shell to a default curl user-agent for a section that renders and for one that does not:

URL default curl UA Googlebot UA
EDOC1100318730/ce945100/cabinet-layout-and-connection-planning 200, 3,800 B, no text 200, 567,916 B, renders
EDOC1100318733/4f560405/cabinet-layout-and-connection-planning 200, 3,800 B, no text 200, 517,177 B, renders

So 200 + shell means not measured. A 404 with the /view/notFound body does discriminate.

2. Under that controlled user-agent, the X8100/X9100 books are absent, not bounced. EDOC1100368229, EDOC1100368230 and EDOC1100305240 answer 404 on the bare root, on a slug with no hash, and on a borrowed topic hash - while sibling books render in the same session, minutes apart. Topic hashes are revision-scoped, so there is no enumeration entry point. The section 12 conclusion holds, now controlled for user-agent.

3. The frame census no longer needs those books. https://e.huawei.com/en/products/storage/oceanprotect/x100-series publishes 2 controllers (X8100) and 4 (X9100), max 4/8 per system, front-end types 16/32/64 Gbit/s FC; 10/25/40/100GE, and node enclosures 86.1 x 447 x 920 mm (2 U) / 175 x 447 x 865 mm (4 U). It publishes no IOM slot count and no per-module port count.

4. The vendor names the tool that would finish it. The readable Interface Module chapter says verbatim: "For details about the types of hot-swappable interface modules supported by each product model, see Spare Parts Query", linking https://info.support.huawei.com/storage/spareparts/#/home. Public page, JavaScript app, needs a browser rather than a fetch. Now the first-listed unblock route, ahead of re-trying the books.

Still missing (#743)

IOM slots that accept front-end interface modules on X8100 (2 U, 2 controllers) and X9100 (4 U, 4 controllers), plus the port count of each 10/25/40/100GE and 16/32/64 Gbit/s FC module fitted to those models. A 2 U frame with an unpublished IOM population would be an empty array, not a census, so nothing is modelled from it.

Gates

  • node scripts/syntax-check.js - 390 files, all OK
  • node scripts/audit-port-types.js - no port contradicts its declared type
  • node scripts/check-control-bytes.js - no control bytes in source
  • catalogue untouched (research-only diff), so docs/DEVICE_REGISTRY.md needs no regeneration
Does **not** close #743 - the IOM census is still unpublished, and no spec is written from research notes. ## What this pass found **1. The probe method was under-controlled.** The support doc viewer returns the *same 3,800-byte SPA shell* to a default `curl` user-agent for a section that renders and for one that does not: | URL | default curl UA | Googlebot UA | |---|---|---| | `EDOC1100318730/ce945100/cabinet-layout-and-connection-planning` | 200, 3,800 B, no text | 200, 567,916 B, renders | | `EDOC1100318733/4f560405/cabinet-layout-and-connection-planning` | 200, 3,800 B, no text | 200, 517,177 B, renders | So `200 + shell` means *not measured*. A `404` with the `/view/notFound` body does discriminate. **2. Under that controlled user-agent, the X8100/X9100 books are absent, not bounced.** `EDOC1100368229`, `EDOC1100368230` and `EDOC1100305240` answer **404** on the bare root, on a slug with no hash, and on a borrowed topic hash - while sibling books render in the same session, minutes apart. Topic hashes are revision-scoped, so there is no enumeration entry point. The section 12 conclusion holds, now controlled for user-agent. **3. The frame census no longer needs those books.** `https://e.huawei.com/en/products/storage/oceanprotect/x100-series` publishes 2 controllers (X8100) and 4 (X9100), max 4/8 per system, front-end types `16/32/64 Gbit/s FC; 10/25/40/100GE`, and node enclosures 86.1 x 447 x 920 mm (2 U) / 175 x 447 x 865 mm (4 U). It publishes no IOM slot count and no per-module port count. **4. The vendor names the tool that would finish it.** The readable Interface Module chapter says verbatim: *"For details about the types of hot-swappable interface modules supported by each product model, see Spare Parts Query"*, linking `https://info.support.huawei.com/storage/spareparts/#/home`. Public page, JavaScript app, needs a browser rather than a fetch. Now the first-listed unblock route, ahead of re-trying the books. ## Still missing (#743) IOM slots that accept front-end interface modules on X8100 (2 U, 2 controllers) and X9100 (4 U, 4 controllers), plus the port count of each 10/25/40/100GE and 16/32/64 Gbit/s FC module fitted to those models. A 2 U frame with an unpublished IOM population would be an empty array, not a census, so nothing is modelled from it. ## Gates - `node scripts/syntax-check.js` - 390 files, all OK - `node scripts/audit-port-types.js` - no port contradicts its declared type - `node scripts/check-control-bytes.js` - no control bytes in source - catalogue untouched (research-only diff), so `docs/DEVICE_REGISTRY.md` needs no regeneration
research(oceanprotect): control the UA when probing doc books, and name the tool the vendor defers to (#743)
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 8s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Docker build (pull_request) Successful in 41s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 6s
69a0f0ae42
A section that renders returns the same 3,800-byte SPA shell to a default curl user-agent as a section that does not exist, so 200+shell is 'not measured', not 'reachable'. With a crawler UA that renders EDOC1100318730 and EDOC1100318733, the X8100/X9100 books (EDOC1100368229, EDOC1100368230, EDOC1100305240) answer 404 on the bare root, on a slug without a hash, and on a borrowed topic hash - absent, not bounced. Frame census for X8100/X9100 is now vendor-sourced from the x100-series spec table (2/4 controllers, max 4/8, 16/32/64G FC + 10/25/40/100GE, 2 U/4 U node sizes); the IOM population is still unpublished, and the Interface Module chapter defers it by name to the public Spare Parts Query tool, which is the next route. No spec written; #743 stays open.
jaylouisw force-pushed catalogue/1117-1555 from 69a0f0ae42
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 8s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Docker build (pull_request) Successful in 41s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 6s
to 3f75f6bcbf
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
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 23s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 20s
2026-11-17 16:03:45 +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!1867
No description provided.