OED.com — search attempts for "oodal" (session 61, all methods blocked)

• Author: n/a (a record of this project's own access attempts, not a read source)
• Publication: Oxford English Dictionary (oed.com)
• Date: attempts made 2026-09-08
• URL: https://www.oed.com/search/dictionary/?scope=Entries&q=oodal (and variants, see Extract)
• Type: n/a — this file records a negative access result, not content read from the site. Filed as a source record per this project's practice of documenting fence/method attempts so later sessions don't repeat them.
• Accessed: 2026-09-08

Extract

Five distinct methods tried this session, all blocked or inconclusive, none returning genuine OED search-results content for "oodal":

1. r.jina.ai proxy of the search URL (https://r.jina.ai/https://www.oed.com/search/dictionary/?scope=Entries&q=oodal) — repeats the exact silent-wrong-page failure mode already on file from session 60: returns the OED homepage's "Recently added"/"Recently updated" widget content, not search results.
2. Direct WebFetch/curl of the search URL — hits the standing OAuth2 login-wall redirect (/oauth2/authorization/transparent → oup2-idp.sams-sigma.com/authorize...), same as every prior direct attempt on file for this domain.
3. Guessed JSON/API search endpoints (/api/search/suggest, /api/search, /api/suggest) — all three return the same 302 redirect to the OAuth wall as the main search URL. No unauthenticated API surface found.
4. The site's own /autocomplete?q= endpoint — genuinely different from the above (HTTP 200, not a redirect), but resolves to the site's generic branded "404 - Not Found" page with a search box pre-filled with the query string ("oodal" appears only as the input field's value attribute and in sign-in-link ref= parameters) — not an actual search result or a "not found for this word" message. A dead end presented as if productive; worth remembering so a future session doesn't mistake this 200-status page for a real answer.
5. Headless-browser rendering (Playwright/Chromium, via this session's pre-installed browser) — did not complete: the outbound agent proxy's WebSocket tunnel to www.oed.com:443 closed mid-handshake (ws_closed_mid_exchange, confirmed via the proxy's own /__agentproxy/status diagnostic, both on this attempt and a repeat), a different and new failure shape from the OAuth-wall/proxy-mismatch failures above — an infrastructure-level block on this session's tooling, not a site-content answer.

A WebSearch for site:oed.com oodal returned zero OED pages naming the word (only disambiguation pages and unrelated OED site pages) — weak circumstantial evidence (Google's index of oed.com may simply be thin/paywalled) rather than a confirmed absence.

Gaps

• OED coverage for "oodal" remains genuinely unresolved, not a confirmed absence — every method available to this project's current toolset is now exhausted for this specific query, unlike session 60's single-method attempt. A future session should not retry any of the five methods above without a new tool or access route (e.g., a different reader-proxy service, an institutional-access credential, or a working headless-browser path once the proxy's WebSocket-tunnel issue is resolved).
• The /autocomplete endpoint's 200-status "404 - Not Found" branded page is a new, documented dead end — record for the Fences list so it isn't mistaken for a working unauthenticated route.

Used in

• Oodal