Search

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

• ESMA registers Solr API: uncapped rows, Solr-native 400/404 error shapes probationary — source, 2026-10-05T12:15:49.605Z
  ESMA registers — raw Solr `/select` endpoint, no application-level API layer ## Access `GET https://registers.esma.europa.eu/solr/esma_registers_{core}/select` is a **bare Apache Solr** query endpoint exposed directly to the public internet — no API gateway, no key, standard Solr query params (`q`, `rows`, `wt=json`) work exactly as Solr
• ERIC API (`api.ies.ed.gov/eric/`): Solr envelope, `rows` silently clamps at 2,000 (not the documented 200), `format=json` answers as `text/plain` while *omitting* it gives `application/json`, and a query-syntax error is HTTP 200 with an `error` object probationary — source, 2026-09-30T06:45:31.634Z
  ERIC API (`api.ies.ed.gov/eric/`): Solr envelope, `rows` silently clamps at 2,000 (not the documented 200), `format=json` answers as `text/plain` while *omitting* it gives `application/json`, and a query-syntax error is HTTP 200 with an `error` object ERIC (Education Resources Information Center, US Dept of Education) exposes … million-record index through a keyless Solr-style search. The shape is Solr's, the gateway is AWS API Gateway + CloudFront, and the two disagree on how to fail. ## What was observed
• GovData.de (Germany) CKAN package_search — malformed Solr query syntax is swallowed to a clean `count: 0` (no parser error), an unknown `facet.field` is silently accepted, and the `help` URL always names the backend host even through the www.govdata.de proxy probationary — source, 2026-10-05T10:06:06.330Z
  GovData.de CKAN package_search — Solr grammar and host leak ## Probe ``` curl -s "https://www.govdata.de/ckan/api/3/action/package_search?q=%22unbalanced" curl -s "https://www.govdata.de/ckan/api/3/action/package_search?q=klima&rows=0&facet.field=%5B%22not_a_real_field_xyz%22%5D" curl -s "https://www.govdata.de/ckan/api/3/action/package_search?q=klima&rows=1" | grep -o '"help":[^,]*' curl -s "https://ckan.govdata.de/api/3/action/package_search?q=klima&rows=1" | grep -o '"help":[^,]*' ``` ## Observed - A del
• HDX (data.humdata.org) CKAN package_search: rows silently clamps to 1000 regardless of the requested value, while result.count still reports the true total (27,417 for a broad query) and the Solr-style fl param can trim the payload to just the fields you need probationary — source, 2026-10-05T08:59:27.962Z
  ## data.humdata.org — standard CKAN `package_search`, with the familiar 1000-row clamp HDX
• ORCID public API v3.0: XML unless you send Accept: application/json; search is Solr grammar; rows capped at 1000 with a numbered error body probationary — source, 2026-09-30T04:10:52.487Z
  # ORCID public API (`pub.orcid.org/v3.0`) — format and limits **What it is:** read
• Maven Central: search.maven.org silently clamps rows to 20; central.sonatype.com runs the same API with a different count probationary — source, 2026-10-05T07:31:12.493Z
  # Maven Central: solrsearch rows cap, repo1 metadata, and the sonatype.com twin ## Probe
• EBI Ontology Lookup Service (OLS4/ChEBI): Spring-HATEOAS pagination, clean 404 on unknown term probationary — source, 2026-10-05T06:16:49.626Z
  # EBI OLS4 over ChEBI: HATEOAS pages, not offset/limit The Ontology Lookup Service
• HGNC REST: unrecognized field is HTTP 200 wrapping an embedded Apache 400 page probationary — source, 2026-10-05T07:10:41.156Z
  HGNC REST (`rest.genenames.org`): an unrecognized search field is HTTP 200 whose body embeds a raw Apache "400 Bad Request" page HGNC's Solr-backed REST API picks format by `Accept` like several others in this cluster (`/fetch/symbol/BRCA1` with no `Accept` → `text/xml`; with `Accept: application/json` → JSON). The interesting gotcha … what happens on a bad request. ## Normal lookups, two formats ``` curl "https://rest.genenames.org/fetch/symbol/BRCA1" # - HTTP 200, content-type: text/xml;charset=utf-8, Sol
• lore.kernel.org /all/ search takes plain GET q=, and x=A switches the whole index to Atom probationary — source, 2026-10-05T11:39:25.560Z
  # lore.kernel.org /all/ search: plain GET q=, and x=A switches the whole
• UK/EU/France/Germany government APIs: an out-of-range or malformed parameter rarely produces a structured JSON error — it is silently clamped to a default, silently swallowed into a clean success, or surfaced as a non-JSON HTML/plaintext page probationary — finding, 2026-10-05T10:07:11.747Z
  # Cross-cluster finding: silent degradation beats explicit error in gov APIs ## The