research(ubiquiti): the Dream Wall Pro has no vendor page, and Ubiquiti serves its 404s as 200s #1781

Merged
jaylouisw merged 1 commit from catalogue/1117-0325 into main 2026-11-17 03:36:14 +00:00
Owner

Refs #130 - research only; this does not close the request.

#130 asks for a Ubiquiti UniFi Dream Wall Pro (UDW-PRO). Its port list was "inferred from the 4gon product name", so nothing in it is sourced. This pass tried to source it from Ubiquiti and found no vendor material for the Pro at all - plus a trap that makes its absence look like a page.

What Ubiquiti publishes is the non-Pro UDW only: https://techspecs.ui.com/unifi/cloud-gateways/udw (200, 704,702 bytes) and https://dl.ui.com/ds/udw_ds.pdf (200, application/pdf, 544,909 bytes) giving (17) LAN GbE RJ45 incl. 4 PoE / 4 PoE+ / 4 PoE++, (1) WAN 2.5 GbE RJ45, (1) LAN + (1) WAN 10G SFP+, 532 W max. That box is already devices/ubiquiti/udw.json.

What does not exist for the Pro:

probe status final URL bytes
techspecs.ui.com/unifi/cloud-gateways/udw-pro 200 https://techspecs.ui.com/ 609,911
store.ui.com/us/en/products/udw-pro 404 unchanged 204,279
dl.ui.com/ds/udw-pro_ds.pdf 200 https://techspecs.ui.com/ 609,911

Two controls run identically - .../udw-pro-techspecs and dl.ui.com/ds/bogus-xyz_ds.pdf - return the same 609,911-byte home page, so on these hosts a 200 is the not-found and only the final URL plus byte count mean anything. The UDW store page contains no udw-pro slug (udw-us, udw-module, udw-raceway only). The 4gon listing the request cites now answers 403.

No spec was added, and UDW-PRO was deliberately not built from the UDW's numbers - LAN count, SFP+ count, PoE budget and bays are precisely the fields the Pro was trailed with differing values for, which is the family-sibling error this project has corrected before.

This PR records the finding so the next pass starts after it: a new research note and a docs/MAINTAINING.md row for the 200-means-404 behaviour.

Blocked on: the Pro's own techspecs page resolving to its own content, its quick-start at a URL that resolves, or Ubiquiti stating it was cancelled (a closable answer; "no census published" is not).

Gates: node scripts/syntax-check.js 373 files OK; node scripts/audit-port-types.js no contradiction; test/hardware-invariants.test.js 26 passed; test/request-queue.test.js 23 passed; check:citations unchanged pre-existing suspects only.

Refs #130 - research only; this does **not** close the request. #130 asks for a Ubiquiti UniFi Dream Wall **Pro** (UDW-PRO). Its port list was "inferred from the 4gon product name", so nothing in it is sourced. This pass tried to source it from Ubiquiti and found no vendor material for the Pro at all - plus a trap that makes its absence look like a page. **What Ubiquiti publishes** is the non-Pro UDW only: `https://techspecs.ui.com/unifi/cloud-gateways/udw` (200, 704,702 bytes) and `https://dl.ui.com/ds/udw_ds.pdf` (200, `application/pdf`, 544,909 bytes) giving (17) LAN GbE RJ45 incl. 4 PoE / 4 PoE+ / 4 PoE++, (1) WAN 2.5 GbE RJ45, (1) LAN + (1) WAN 10G SFP+, 532 W max. That box is already `devices/ubiquiti/udw.json`. **What does not exist for the Pro:** | probe | status | final URL | bytes | |---|---|---|---| | `techspecs.ui.com/unifi/cloud-gateways/udw-pro` | 200 | `https://techspecs.ui.com/` | 609,911 | | `store.ui.com/us/en/products/udw-pro` | **404** | unchanged | 204,279 | | `dl.ui.com/ds/udw-pro_ds.pdf` | 200 | `https://techspecs.ui.com/` | 609,911 | Two controls run identically - `.../udw-pro-techspecs` and `dl.ui.com/ds/bogus-xyz_ds.pdf` - return the *same* 609,911-byte home page, so on these hosts a 200 is the not-found and only the final URL plus byte count mean anything. The UDW store page contains no `udw-pro` slug (`udw-us`, `udw-module`, `udw-raceway` only). The 4gon listing the request cites now answers 403. **No spec was added**, and `UDW-PRO` was deliberately not built from the UDW's numbers - LAN count, SFP+ count, PoE budget and bays are precisely the fields the Pro was trailed with differing values for, which is the family-sibling error this project has corrected before. This PR records the finding so the next pass starts after it: a new research note and a `docs/MAINTAINING.md` row for the 200-means-404 behaviour. Blocked on: the Pro's own techspecs page resolving to its own content, its quick-start at a URL that resolves, or Ubiquiti stating it was cancelled (a closable answer; "no census published" is not). Gates: `node scripts/syntax-check.js` 373 files OK; `node scripts/audit-port-types.js` no contradiction; `test/hardware-invariants.test.js` 26 passed; `test/request-queue.test.js` 23 passed; `check:citations` unchanged pre-existing suspects only.
research(ubiquiti): the Dream Wall Pro has no vendor page, and Ubiquiti serves its 404s as 200s (#130)
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Docker build (pull_request) Successful in 22s
CI / Arm auto-merge (pull_request) Successful in 11s
38487cf9ac
jaylouisw force-pushed catalogue/1117-0325 from 38487cf9ac
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Docker build (pull_request) Successful in 22s
CI / Arm auto-merge (pull_request) Successful in 11s
to 9a088f81f1
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Test (Node 22) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 17s
2026-11-17 03:32:18 +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!1781
No description provided.