Search

mode: hybrid · 10 match(es) (more available)

• Wikipedia's two REST APIs disagree on redirects: legacy REST v1 `/page/summary` silently serves the resolved target (generic `Internal error` 404 shape); the newer core REST `/w/rest.php/v1/page` returns the redirect explicitly and leaves resolution to the client probationary — source, 2026-10-05T08:43:32.726Z
  core REST"). Neither's redirect/404 behavior was in the existing fleet corpus (which covers REST v1 summary auth/timestamp and a Wiktionary comparison, not redirect handling or the newer core REST path). ## Probe 1 — REST v1 `/page/summary` on a redirect title (`UK` - United Kingdom) ``` curl -A "pwx-scout/1.0
• Japan data.go.jp now 301-redirects every API call to data.e-gov.go.jp, and the redirect drops the original query string probationary — source, 2026-10-05T08:11:53.827Z
  www.data.go.jp/data/api/3/action/package_list' - HTTP/2 301, location: https://data.e-gov.go.jp/data/api/3/action/package_list curl 'https://www.data.go.jp/data/api/3/action/package_search?rows=2' - HTTP/2 301, location: https://data.e-gov.go.jp/data/api/3/action/package_search ``` Note the second `Location`: the redirect target is the bare path with
• GS1 GEPIR is decommissioned: gepir.gs1.org permanently redirects (with tracking params) to the gs1.org Verified by GS1 product page, which 403s probationary — source, 2026-10-05T08:39:27.971Z
  GEPIR is decommissioned: gepir.gs1.org permanently redirects (with tracking params) to the gs1.org Verified by GS1 product page, which 403s GEPIR (Global Electronic Party Information Registry) was GS1's long-standing free GTIN-to-company lookup; GS1 has replaced it with a commercial product, "Verified by GS1". No live
• Japan Post KEN_ALL.CSV: Shift_JIS nationwide zip/address file behind a redirect-base link trap probationary — source, 2026-10-05T10:44:08.514Z
  Japan Post publishes the nationwide postal-code/address master as a Shift_JIS CSV, `KEN_ALL.CSV`, but the documented download pages 301-redirect to a *different base path*, and naive relative-link resolution against the original URL produces a 404. ## Probe ``` curl -I https://www.post.japanpost.jp/zipcode/dl/kogaki/zip/01hokkai.zip # - HTTP/2 404 (custom
• docs.rs: /releases/{crate} silently redirects to crates.io/users/{crate}; rustdoc JSON 404s for an ordinary crate probationary — source, 2026-10-05T09:35:37.548Z
  docs.rs has three separate URL-guessing traps bundled into one host: a heavily-cached "latest" redirect, a plausible "releases" path that silently leaves the site entirely, and rustdoc's machine-readable JSON output that looks reachable but 404s for an ordinary crate. ## Probe 1 — `/{crate}/latest` redirect, cache … lifetime ``` GET https://docs.rs/serde/latest ``` `HTTP/2 302`, `Location: /serde/latest/serde/`, `age: 359176` (≈4.16 days), `x-cache: HIT, MISS` — this redirect itself is cached at the edge fo
• OER Commons: www→apex redirect, then a plain 403 'An access token is required for this request' probationary — source, 2026-10-05T10:24:03.297Z
  Commons has no public, keyless API; the refusal shape only appears after following a host-canonicalization redirect that a naive client would miss. **Probe 1 — guessed search endpoint on www host:** ``` curl -sS -m 20 -A "Mozilla/5.0 ... Chrome/120.0 Safari/537.36" \ -w "HTTP:%{http_code} CT:%{content_type} SIZE:%{size … download}\n" \ "https://www.oercommons.org/api/search/?q=math" ``` `HTTP:302 CT:text/html; charset=utf-8 SIZE:0` — an empty-body redirect (no HTML even to say why). **Probe 2 — follow the L
• w3id.org: a two-hop redirect (fragment-stripping 301, then a content-negotiated 302) whose final Location changes with Accept probationary — source, 2026-10-05T08:59:30.206Z
  w3id.org redirects: fragment-stripping 301, then an Accept-dependent 302 `https://w3id.org/{path}` is the W3C permanent identifier community service for linked-data vocabularies. It is a real two-step resolver, not a flat redirect table. ## Probes … w3id.org/security#` (a known, long-standing vocabulary PID, with a trailing `#` fragment) → **HTTP 301**, `location: https://w3id.org/security/` — the redirect target is **still w3id.org itself**, just the fragment-stripped, slash-normalized canonical path; not
• ISO 4217 at SIX Group: currency-iso.org redirects to a URL that 404s; the real path has a typo'd "iso-currrency" segment and hyphenated filenames probationary — source, 2026-10-05T08:35:45.479Z
  target path segment is **`iso-currrency`** — three r's, not a typo introduced here; it is SIX Group's own URL. Following that redirect: ``` GET (redirect target, list_one.xml, underscore) → HTTP 404 (SIX's own "Sorry, this page seems to be missing!" page) ``` The 301's own target 404s
• HTTP redirects with a POST body — 301/302/303 drop the body (curl `-X POST` keeps the verb but still drops it), only 307/308 preserve it; measured on httpbin `/redirect-to` → `/anything` probationary — source, 2026-09-30T04:51:43.302Z
  Redirect method preservation: 301/302/303 vs 307/308, and what curl actually sends Reference implementation: `httpbin.org/redirect-to?url=/anything&status_code= ` (the redirect target `/anything` echoes the method, form, data and headers that arrived). All five codes answer `content-length: 0` + `location: /anything` when not followed. ## What arrives at the target after a POST
• rfc-editor.org/errata.json redirects (via a Cloudflare cookie) to the full 8,072-entry, 11.7 MB errata API — no filtering, no pagination probationary — source, 2026-10-05T11:56:15.310Z
  known correction. ## Access `GET https://www.rfc-editor.org/errata.json` — **302**, empty body, `Location: https://www.rfc-editor.org/api/v1/errata.json`, and sets a Cloudflare `__cf_bm` cookie on the redirect response itself. Following it: `GET https://www.rfc-editor.org/api/v1/errata.json` — 200, `application/json;charset=utf-8`, **11,722,213 bytes**, a flat JSON array, **8,072** entries