@lde/iiif-validator 0.1.1 → 0.1.3

package/README.md

@@ -28,7 +28,7 @@ interface ManifestValidation {
 
 ## Behaviour
 
-- **Dereference over HTTP** with `Accept: application/ld+json, application/json`, following redirects, using the global `fetch` with an `AbortSignal` timeout (default 10 000 ms). Both are injectable via the options argument (`fetch`, `timeoutMs`).
+- **Dereference over HTTP** with `Accept: */*`, following redirects, using the global `fetch` with an `AbortSignal` timeout (default 10 000 ms). The wildcard mirrors what real IIIF viewers send (the browser `fetch` default); a JSON-specific `Accept` would be more correct but trips up hosts that do backwards content negotiation – serving the manifest to `*/*` while returning 404 for a JSON-specific request. Both `fetch` and `timeoutMs` are injectable via the options argument.
 - **Lightweight, version-aware structural check.** A document is valid when the response is HTTP 2xx, the body parses as JSON, its `@context` references an IIIF Presentation context, and its `type`/`@type` indicates a manifest – accepting both v3 (`Manifest`) and v2 (`sc:Manifest`). The `@context` value may be a string, an array, or an object; all forms are handled. The version segment of the context is accepted version-agnostically.
 - **Strict failure semantics, no retries.** A timeout, network error, non-2xx status, unparseable body, missing IIIF `@context`, or wrong `type` all yield `valid: false` with the corresponding coarse `reason`. There is no deep JSON Schema validation and no dependency on the hosted IIIF Presentation Validator service.
 

package/dist/validateManifest.d.ts

@@ -3,7 +3,7 @@
  * *what kind* of failure occurred, not a detailed diagnosis — only enough to
  * tell apart an unreachable host from a malformed document.
  */
-export type ManifestValidationReason = 'valid-manifest' | 'timeout' | 'network-error' | 'http-error' | 'invalid-json' | 'not-a-manifest';
+export type ManifestValidationReason = 'valid-manifest' | 'timeout' | 'network-error' | 'http-error' | 'invalid-json' | 'binary-content' | 'not-a-manifest';
 /**
  * Verdict returned by {@link validateManifest}.
  */

package/dist/validateManifest.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"validateManifest.d.ts","sourceRoot":"","sources":["../src/validateManifest.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,MAAM,MAAM,wBAAwB,GAChC,gBAAgB,GAChB,SAAS,GACT,eAAe,GACf,YAAY,GACZ,cAAc,GACd,gBAAgB,CAAC;AAErB;;GAEG;AACH,MAAM,WAAW,kBAAkB;IACjC,0EAA0E;IAC1E,KAAK,EAAE,OAAO,CAAC;IACf,4CAA4C;IAC5C,MAAM,EAAE,wBAAwB,CAAC;CAClC;AAED;;GAEG;AACH,MAAM,WAAW,uBAAuB;IACtC;;;OAGG;IACH,KAAK,CAAC,EAAE,OAAO,UAAU,CAAC,KAAK,CAAC;IAChC,+DAA+D;IAC/D,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAKD;;;;GAIG;AACH,wBAAsB,gBAAgB,CACpC,GAAG,EAAE,MAAM,EACX,OAAO,CAAC,EAAE,uBAAuB,GAChC,OAAO,CAAC,kBAAkB,CAAC,CA6B7B"}
+{"version":3,"file":"validateManifest.d.ts","sourceRoot":"","sources":["../src/validateManifest.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,MAAM,MAAM,wBAAwB,GAChC,gBAAgB,GAChB,SAAS,GACT,eAAe,GACf,YAAY,GACZ,cAAc,GACd,gBAAgB,GAChB,gBAAgB,CAAC;AAErB;;GAEG;AACH,MAAM,WAAW,kBAAkB;IACjC,0EAA0E;IAC1E,KAAK,EAAE,OAAO,CAAC;IACf,4CAA4C;IAC5C,MAAM,EAAE,wBAAwB,CAAC;CAClC;AAED;;GAEG;AACH,MAAM,WAAW,uBAAuB;IACtC;;;OAGG;IACH,KAAK,CAAC,EAAE,OAAO,UAAU,CAAC,KAAK,CAAC;IAChC,+DAA+D;IAC/D,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAKD;;;;GAIG;AACH,wBAAsB,gBAAgB,CACpC,GAAG,EAAE,MAAM,EACX,OAAO,CAAC,EAAE,uBAAuB,GAChC,OAAO,CAAC,kBAAkB,CAAC,CA8C7B"}

package/dist/validateManifest.js

@@ -11,7 +11,13 @@ export async function validateManifest(url, options) {
     let response;
     try {
         response = await doFetch(url, {
-            headers: { Accept: 'application/ld+json, application/json' },
+            // Request with `Accept: */*`, matching what real IIIF viewers (Mirador,
+            // Universal Viewer) send via the browser `fetch` default. A more specific
+            // `application/ld+json` is technically correct, but some manifest hosts do
+            // backwards content negotiation: they serve the manifest to `*/*` yet 404
+            // a JSON-specific request. Asking for anything keeps the validator as
+            // permissive as the viewers whose access it stands in for.
+            headers: { Accept: '*/*' },
             signal: AbortSignal.timeout(timeoutMs),
         });
     }
@@ -21,6 +27,16 @@ export async function validateManifest(url, options) {
     if (!response.ok) {
         return { valid: false, reason: 'http-error' };
     }
+    // A manifest is JSON. When the server announces a binary media type, skip
+    // reading the body: a sampled `schema:contentUrl` can dereference to the
+    // full-resolution image, audio or video asset, and `response.json()` would
+    // buffer the whole thing before failing to parse it — wasting bandwidth and
+    // time in the pipeline that calls this for every sampled manifest. Cancel the
+    // stream so the connection is freed without the download.
+    if (isBinaryMedia(response.headers.get('content-type'))) {
+        await response.body?.cancel();
+        return { valid: false, reason: 'binary-content' };
+    }
     let body;
     try {
         body = await response.json();
@@ -33,6 +49,20 @@ export async function validateManifest(url, options) {
     }
     return { valid: false, reason: 'not-a-manifest' };
 }
+/**
+ * Whether a `Content-Type` header announces a binary media asset (image, audio
+ * or video) rather than a JSON document. Used to skip downloading non-manifest
+ * media. A missing or ambiguous type (e.g. `text/plain`, `application/octet-stream`)
+ * returns `false` so a manifest served with an odd type is still parsed.
+ */
+function isBinaryMedia(contentType) {
+    if (contentType === null)
+        return false;
+    const mediaType = contentType.toLowerCase();
+    return (mediaType.startsWith('image/') ||
+        mediaType.startsWith('audio/') ||
+        mediaType.startsWith('video/'));
+}
 /**
  * Classify a thrown `fetch` error. An aborted request (our own
  * `AbortSignal.timeout` firing, surfaced as `AbortError`/`TimeoutError`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lde/iiif-validator",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "repository": {
     "url": "git+https://github.com/ldelements/lde.git",
     "directory": "packages/iiif-validator"