research(ubiquiti): the storefront 404 is a control slug, not a stored hash (#130) #2324
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!2324
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1120-2222"
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 #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:
store.ui.com/us/en/products/udwstore.ui.com/us/en/products/udw-proLocationstore.ui.com/us/en/products/xzqv-nonexistent-skustore.ui.com/us/en/pro/products/udwLocation: .../us/en/products/udwThe 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, andresearch/open-device-requests.jsonnow says so instead of quoting a stale fingerprint.Also recorded:
/us/en/pro/products/udwstill 308s to the canonical route, so the archived/pro/path is an alias, not a product tree; andproducts.json,sitemap_products_1.xml,collections/all/products.jsonall 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 withdevices/ubiquiti/udw.jsonon 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). ItsMax. WAN Port Count = 8withDefault 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.mdregenerated from the JSON, not hand-edited.Gates:
node scripts/syntax-check.js500 files OK;audit-port-types.js0 gated;audit-devices.js0 gated;test/hardware-invariants.test.js26 passed;test/request-queue.test.js32 passed.