research(ubiquiti): the storefront 404 is a control slug, not a stored hash (#130) #2324

Merged
jaylouisw merged 1 commit from catalogue/1120-2222 into main 2026-11-20 22:38:25 +00:00
Owner

Refs #130 only - this does not close the request, and no device spec is added or changed. The Dream Wall Pro is still absent from every Ubiquiti surface; what changes here is the test that says so.

The storefront, measured with a control slug instead of a stored hash

Measured 2026-11-20 ~22:20Z, redirects not followed, bot UA and desktop Chrome UA give identical results:

URL status bytes note
store.ui.com/us/en/products/udw 200 568,234 live product page
store.ui.com/us/en/products/udw-pro 404 213,322 at the requested URL, no Location
store.ui.com/us/en/products/xzqv-nonexistent-sku 404 213,322 control - byte-identical body
store.ui.com/us/en/pro/products/udw 308 39 Location: .../us/en/products/udw

The not-found shell is 213,322 B today against the 204,478 B / md5 39388de6395c... recorded on 2026-11-19/20: the storefront was rebuilt in between and its 404 page grew 8,844 bytes. A pass comparing a stored hash would have read that difference as a product appearing. The durable test is the impossible slug run in the same minute, and research/open-device-requests.json now says so instead of quoting a stale fingerprint.

Also recorded: /us/en/pro/products/udw still 308s to the canonical route, so the archived /pro/ path is an alias, not a product tree; and products.json, sitemap_products_1.xml, collections/all/products.json all 307/308 away - the store is a Next.js app (motif-theme, assets.ecomm.ui.com), not Shopify, so there is no product API to enumerate.

No spec change - and the payload says why

The live product payload (__NEXT_DATA__ -> props.pageProps.collection.products[0].technicalSpecification) agrees with devices/ubiquiti/udw.json on all six port/PoE/WiFi rows the datasheet publishes (17 GbE at 4 PoE++/4 PoE+/4 PoE, 1x 2.5G, 2x 10G SFP+, 420 W budget, 112 W excluding PoE, 5 GHz 4x4 / 2.4 GHz 2x2). Its Max. WAN Port Count = 8 with Default WAN Ports = (1) 2.5 GbE / (1) 10G SFP+ names a ceiling and the shipped defaults but no per-port rule, so the seventeen GbE ports are not marked WAN-capable: a guess there would let a lab cable nine uplinks the vendor caps at eight.

Evidence: research/ubiquiti-storefront-product-payload.md. docs/DEVICE_REGISTRY.md regenerated from the JSON, not hand-edited.

Gates: node scripts/syntax-check.js 500 files OK; audit-port-types.js 0 gated; audit-devices.js 0 gated; test/hardware-invariants.test.js 26 passed; test/request-queue.test.js 32 passed.

Refs #130 only - this does not close the request, and no device spec is added or changed. The Dream Wall Pro is still absent from every Ubiquiti surface; what changes here is the *test* that says so. ## The storefront, measured with a control slug instead of a stored hash Measured 2026-11-20 ~22:20Z, redirects not followed, bot UA and desktop Chrome UA give identical results: | URL | status | bytes | note | |---|---|---|---| | `store.ui.com/us/en/products/udw` | 200 | 568,234 | live product page | | `store.ui.com/us/en/products/udw-pro` | **404** | 213,322 | at the requested URL, no `Location` | | `store.ui.com/us/en/products/xzqv-nonexistent-sku` | **404** | 213,322 | control - byte-identical body | | `store.ui.com/us/en/pro/products/udw` | **308** | 39 | `Location: .../us/en/products/udw` | The not-found shell is **213,322 B** today against the **204,478 B / md5 `39388de6395c...`** recorded on 2026-11-19/20: the storefront was rebuilt in between and its 404 page grew 8,844 bytes. A pass comparing a stored hash would have read that difference as a product appearing. The durable test is the impossible slug run in the same minute, and `research/open-device-requests.json` now says so instead of quoting a stale fingerprint. Also recorded: `/us/en/pro/products/udw` still 308s to the canonical route, so the archived `/pro/` path is an alias, not a product tree; and `products.json`, `sitemap_products_1.xml`, `collections/all/products.json` all 307/308 away - the store is a Next.js app (`motif-theme`, `assets.ecomm.ui.com`), not Shopify, so there is no product API to enumerate. ## No spec change - and the payload says why The live product payload (`__NEXT_DATA__` -> `props.pageProps.collection.products[0].technicalSpecification`) agrees with `devices/ubiquiti/udw.json` on all six port/PoE/WiFi rows the datasheet publishes (17 GbE at 4 PoE++/4 PoE+/4 PoE, 1x 2.5G, 2x 10G SFP+, 420 W budget, 112 W excluding PoE, 5 GHz 4x4 / 2.4 GHz 2x2). Its `Max. WAN Port Count = 8` with `Default WAN Ports = (1) 2.5 GbE / (1) 10G SFP+` names a ceiling and the shipped defaults but no per-port rule, so the seventeen GbE ports are not marked WAN-capable: a guess there would let a lab cable nine uplinks the vendor caps at eight. Evidence: `research/ubiquiti-storefront-product-payload.md`. `docs/DEVICE_REGISTRY.md` regenerated from the JSON, not hand-edited. Gates: `node scripts/syntax-check.js` 500 files OK; `audit-port-types.js` 0 gated; `audit-devices.js` 0 gated; `test/hardware-invariants.test.js` 26 passed; `test/request-queue.test.js` 32 passed.
research(ubiquiti): the storefront 404 is a control slug, not a stored hash (#130)
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Successful in 1m2s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Test (Node 18) (pull_request) Successful in 1m9s
CI / Server smoke and Docker build (pull_request) Successful in 39s
CI / Arm auto-merge (pull_request) Successful in 4s
b6e3786bcf
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 22:30:17 +00:00
jaylouisw deleted branch catalogue/1120-2222 2026-11-20 22:38:28 +00:00
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!2324
No description provided.