@kensio/yulin 1.21.3 → 1.21.5

package/dist/service/s3/error/sim-s3-upload.error.d.ts

@@ -0,0 +1,41 @@
+import { SimS3Error } from "./sim-s3.error.js";
+/**
+ * The errors a multipart upload answers with.
+ *
+ * An upload is the one S3 operation made of several requests, so these are
+ * about the upload as a whole rather than about one Object or one Bucket.
+ */
+/**
+ * Simulated S3 NoSuchUpload error.
+ *
+ * What real S3 answers when a request names a multipart upload id it did not
+ * issue, or one belonging to an upload that has since been completed or
+ * aborted.
+ */
+export declare class SimS3NoSuchUpload extends SimS3Error {
+    readonly name = "NoSuchUpload";
+    constructor(message: string);
+}
+/**
+ * Simulated S3 InvalidPart error.
+ *
+ * A completion naming a part that was never uploaded, or naming an ETag other
+ * than the one that part was stored under. Real S3 refuses rather than
+ * assembling what it can, because a caller that lost a part should not end up
+ * with an Object silently missing its middle.
+ */
+export declare class SimS3InvalidPart extends SimS3Error {
+    readonly name = "InvalidPart";
+    constructor(message: string);
+}
+/**
+ * Simulated S3 InvalidPartOrder error.
+ *
+ * A completion listing its parts in an order other than ascending part number.
+ * The parts themselves can be uploaded in any order; it is the list in the
+ * completion request that real S3 requires to be sorted.
+ */
+export declare class SimS3InvalidPartOrder extends SimS3Error {
+    readonly name = "InvalidPartOrder";
+    constructor(message: string);
+}

package/dist/service/s3/error/sim-s3-upload.error.js

@@ -0,0 +1,47 @@
+import { SimS3Error } from "./sim-s3.error.js";
+/**
+ * The errors a multipart upload answers with.
+ *
+ * An upload is the one S3 operation made of several requests, so these are
+ * about the upload as a whole rather than about one Object or one Bucket.
+ */
+/**
+ * Simulated S3 NoSuchUpload error.
+ *
+ * What real S3 answers when a request names a multipart upload id it did not
+ * issue, or one belonging to an upload that has since been completed or
+ * aborted.
+ */
+export class SimS3NoSuchUpload extends SimS3Error {
+    name = "NoSuchUpload";
+    constructor(message) {
+        super(message, { httpStatusCode: 404 });
+    }
+}
+/**
+ * Simulated S3 InvalidPart error.
+ *
+ * A completion naming a part that was never uploaded, or naming an ETag other
+ * than the one that part was stored under. Real S3 refuses rather than
+ * assembling what it can, because a caller that lost a part should not end up
+ * with an Object silently missing its middle.
+ */
+export class SimS3InvalidPart extends SimS3Error {
+    name = "InvalidPart";
+    constructor(message) {
+        super(message, { httpStatusCode: 400 });
+    }
+}
+/**
+ * Simulated S3 InvalidPartOrder error.
+ *
+ * A completion listing its parts in an order other than ascending part number.
+ * The parts themselves can be uploaded in any order; it is the list in the
+ * completion request that real S3 requires to be sorted.
+ */
+export class SimS3InvalidPartOrder extends SimS3Error {
+    name = "InvalidPartOrder";
+    constructor(message) {
+        super(message, { httpStatusCode: 400 });
+    }
+}

package/dist/service/s3/error/sim-s3.error.d.ts

@@ -136,6 +136,16 @@ export declare class SimS3InvalidArgument extends SimS3Error {
     readonly name = "InvalidArgument";
     constructor(message: string);
 }
+/**
+ * Simulated S3 InvalidStorageClass error.
+ *
+ * Real S3 answers this for a write naming a storage class it has no such class
+ * for, and refuses the write rather than storing the Object in the default one.
+ */
+export declare class SimS3InvalidStorageClass extends SimS3Error {
+    readonly name = "InvalidStorageClass";
+    constructor(message: string);
+}
 /**
  * Simulated S3 NotImplemented error.
  *
@@ -153,40 +163,6 @@ export declare class SimS3InvalidBucketName extends SimS3Error {
     readonly name = "InvalidBucketName";
     constructor(message: string);
 }
-/**
- * Simulated S3 NoSuchUpload error.
- *
- * What real S3 answers when a request names a multipart upload id it did not
- * issue, or one belonging to an upload that has since been completed or
- * aborted.
- */
-export declare class SimS3NoSuchUpload extends SimS3Error {
-    readonly name = "NoSuchUpload";
-    constructor(message: string);
-}
-/**
- * Simulated S3 InvalidPart error.
- *
- * A completion naming a part that was never uploaded, or naming an ETag other
- * than the one that part was stored under. Real S3 refuses rather than
- * assembling what it can, because a caller that lost a part should not end up
- * with an Object silently missing its middle.
- */
-export declare class SimS3InvalidPart extends SimS3Error {
-    readonly name = "InvalidPart";
-    constructor(message: string);
-}
-/**
- * Simulated S3 InvalidPartOrder error.
- *
- * A completion listing its parts in an order other than ascending part number.
- * The parts themselves can be uploaded in any order; it is the list in the
- * completion request that real S3 requires to be sorted.
- */
-export declare class SimS3InvalidPartOrder extends SimS3Error {
-    readonly name = "InvalidPartOrder";
-    constructor(message: string);
-}
 /**
  * Simulated S3 InvalidRange error.
  *
@@ -211,3 +187,15 @@ export declare class SimS3InvalidRequest extends SimS3Error {
     readonly name = "InvalidRequest";
     constructor(message: string);
 }
+/**
+ * Simulated S3 InvalidTag error.
+ *
+ * Real S3 answers this for a tag set it will not hold against an Object: more
+ * than ten tags, or two tags under one key. The write is refused rather than
+ * partly applied, so a caller that sent eleven tags does not find ten of them
+ * on the Object.
+ */
+export declare class SimS3InvalidTag extends SimS3Error {
+    readonly name = "InvalidTag";
+    constructor(message: string);
+}

package/dist/service/s3/error/sim-s3.error.js

@@ -159,6 +159,18 @@ export class SimS3InvalidArgument extends SimS3Error {
         super(message, { httpStatusCode: 400 });
     }
 }
+/**
+ * Simulated S3 InvalidStorageClass error.
+ *
+ * Real S3 answers this for a write naming a storage class it has no such class
+ * for, and refuses the write rather than storing the Object in the default one.
+ */
+export class SimS3InvalidStorageClass extends SimS3Error {
+    name = "InvalidStorageClass";
+    constructor(message) {
+        super(message, { httpStatusCode: 400 });
+    }
+}
 /**
  * Simulated S3 NotImplemented error.
  *
@@ -180,46 +192,6 @@ export class SimS3InvalidBucketName extends SimS3Error {
         super(message, { httpStatusCode: 400 });
     }
 }
-/**
- * Simulated S3 NoSuchUpload error.
- *
- * What real S3 answers when a request names a multipart upload id it did not
- * issue, or one belonging to an upload that has since been completed or
- * aborted.
- */
-export class SimS3NoSuchUpload extends SimS3Error {
-    name = "NoSuchUpload";
-    constructor(message) {
-        super(message, { httpStatusCode: 404 });
-    }
-}
-/**
- * Simulated S3 InvalidPart error.
- *
- * A completion naming a part that was never uploaded, or naming an ETag other
- * than the one that part was stored under. Real S3 refuses rather than
- * assembling what it can, because a caller that lost a part should not end up
- * with an Object silently missing its middle.
- */
-export class SimS3InvalidPart extends SimS3Error {
-    name = "InvalidPart";
-    constructor(message) {
-        super(message, { httpStatusCode: 400 });
-    }
-}
-/**
- * Simulated S3 InvalidPartOrder error.
- *
- * A completion listing its parts in an order other than ascending part number.
- * The parts themselves can be uploaded in any order; it is the list in the
- * completion request that real S3 requires to be sorted.
- */
-export class SimS3InvalidPartOrder extends SimS3Error {
-    name = "InvalidPartOrder";
-    constructor(message) {
-        super(message, { httpStatusCode: 400 });
-    }
-}
 /**
  * Simulated S3 InvalidRange error.
  *
@@ -248,3 +220,17 @@ export class SimS3InvalidRequest extends SimS3Error {
         super(message, { httpStatusCode: 400 });
     }
 }
+/**
+ * Simulated S3 InvalidTag error.
+ *
+ * Real S3 answers this for a tag set it will not hold against an Object: more
+ * than ten tags, or two tags under one key. The write is refused rather than
+ * partly applied, so a caller that sent eleven tags does not find ten of them
+ * on the Object.
+ */
+export class SimS3InvalidTag extends SimS3Error {
+    name = "InvalidTag";
+    constructor(message) {
+        super(message, { httpStatusCode: 400 });
+    }
+}

package/dist/service/s3/mount/sim-s3-mount.type.d.ts

@@ -28,6 +28,16 @@ export interface SimS3MountFilesystemOptions {
      * build one reload. The default suits a generator writing its output.
      */
     readonly settleMs?: number | undefined;
+    /**
+     * Let a DeleteObject remove the file behind an Object key.
+     *
+     * A mounted Bucket refuses a delete by default, because the files under the
+     * directory are the user's own and a test that empties a Bucket would empty
+     * their build output with it. A mount that says so gets the deletion an
+     * in-memory Bucket performs, event notification included, within the same
+     * key and extension checks a read goes through.
+     */
+    readonly allowDelete?: boolean | undefined;
     /**
      * File extensions to serve in addition to the usual web ones.
      *

package/dist/service/s3/notification/event/sim-s3-event-records.d.ts

@@ -45,7 +45,8 @@ export declare function simS3EventRequestId(): string;
 /**
  * The object key as a record carries it.
  *
- * Real S3 form-URL-encodes the key, so a space becomes a plus sign, while the
- * slashes that make up a key prefix stay as they are.
+ * A record carries the key encoded, the same way a listing asked for one does,
+ * so a function reading a record has to decode it before the key names an
+ * Object.
  */
 export declare function simS3EventObjectKey(key: string): string;

package/dist/service/s3/notification/event/sim-s3-event-records.js

@@ -1,4 +1,5 @@
 import { randomUUID } from "node:crypto";
+import { simS3EncodedKey } from "../../object/s3-key-encoding.js";
 /**
  * The event structure version this simulator emits.
  *
@@ -84,9 +85,10 @@ export function simS3EventRequestId() {
 /**
  * The object key as a record carries it.
  *
- * Real S3 form-URL-encodes the key, so a space becomes a plus sign, while the
- * slashes that make up a key prefix stay as they are.
+ * A record carries the key encoded, the same way a listing asked for one does,
+ * so a function reading a record has to decode it before the key names an
+ * Object.
  */
 export function simS3EventObjectKey(key) {
-    return encodeURIComponent(key).replaceAll("%20", "+").replaceAll("%2F", "/");
+    return simS3EncodedKey(key);
 }

package/dist/service/s3/notification/event/sim-s3-object-event-builder.d.ts

@@ -5,25 +5,40 @@ import type { SimS3Bucket } from "../../bucket/sim-s3-bucket.js";
 import type { SimS3Object } from "../../object/s3-object.js";
 import { SimS3ObjectEvent } from "./sim-s3-object-event.js";
 /**
- * An Object a command has just stored.
+ * An Object a command has just written, in whatever sense.
+ *
+ * Storing the bytes and retagging them are both writes to an Object that
+ * exists, so both events describe the same thing: the Object as it now stands.
+ * The event name is what tells the two apart.
  */
-export interface SimS3ObjectCreatedInput {
+interface SimS3WrittenObjectInput<Event extends SimS3NotificationEvent> {
     readonly bucket: SimS3Bucket;
     readonly object: SimS3Object;
     readonly caller: SimAwsResolvedCaller;
-    /**
-     * How the Object came to be there, which real S3 distinguishes: an Object
-     * assembled from parts arrives as `s3:ObjectCreated:CompleteMultipartUpload`
-     * rather than as a Put.
-     */
-    readonly eventName: SimS3ObjectCreatedEvent;
+    readonly eventName: Event;
     /** The version the write was given, on a Bucket keeping versions. */
     readonly versionId?: string | undefined;
 }
+/**
+ * An Object a command has just stored.
+ *
+ * The event name says how the Object came to be there, which real S3
+ * distinguishes: an Object assembled from parts arrives as
+ * `s3:ObjectCreated:CompleteMultipartUpload` rather than as a Put.
+ */
+export type SimS3ObjectCreatedInput = SimS3WrittenObjectInput<SimS3ObjectCreatedEvent>;
+/**
+ * An Object whose tags a command has just replaced.
+ */
+export type SimS3ObjectTaggedInput = SimS3WrittenObjectInput<SimS3ObjectTaggingEvent>;
 /**
  * The ways an Object can be created that simulated S3 raises an event for.
  */
 export type SimS3ObjectCreatedEvent = Extract<SimS3NotificationEvent, `s3:ObjectCreated:${string}`>;
+/**
+ * The ways an Object's tags can change that simulated S3 raises an event for.
+ */
+type SimS3ObjectTaggingEvent = Extract<SimS3NotificationEvent, `s3:ObjectTagging:${string}`>;
 /**
  * The ways an Object can be removed that simulated S3 raises an event for.
  */
@@ -77,11 +92,21 @@ export declare class SimS3ObjectEventBuilder {
      * size and ETag.
      */
     forCreated(input: SimS3ObjectCreatedInput): SimS3ObjectEvent;
+    /**
+     * Build the event for an Object whose tags were replaced, which carries the
+     * same size and ETag a creation does.
+     *
+     * Real S3 describes the Object the tags now sit on, and tagging changes
+     * neither of those, so a tagging record and the creation record before it
+     * report the same bytes.
+     */
+    forTagged(input: SimS3ObjectTaggedInput): SimS3ObjectEvent;
     /**
      * Build the event for an Object that was removed, which carries neither size
      * nor ETag, because the Object they described is gone.
      */
     forRemoved(input: SimS3ObjectRemovedInput): SimS3ObjectEvent;
+    private forWritten;
     private build;
 }
 export {};

package/dist/service/s3/notification/event/sim-s3-object-event-builder.js

@@ -21,15 +21,18 @@ export class SimS3ObjectEventBuilder {
      * size and ETag.
      */
     forCreated(input) {
-        return this.build({
-            bucket: input.bucket,
-            eventName: input.eventName,
-            key: input.object.key,
-            caller: input.caller,
-            size: input.object.body.length,
-            eTag: input.object.etag,
-            versionId: input.versionId,
-        });
+        return this.forWritten(input);
+    }
+    /**
+     * Build the event for an Object whose tags were replaced, which carries the
+     * same size and ETag a creation does.
+     *
+     * Real S3 describes the Object the tags now sit on, and tagging changes
+     * neither of those, so a tagging record and the creation record before it
+     * report the same bytes.
+     */
+    forTagged(input) {
+        return this.forWritten(input);
     }
     /**
      * Build the event for an Object that was removed, which carries neither size
@@ -44,6 +47,17 @@ export class SimS3ObjectEventBuilder {
             versionId: input.versionId,
         });
     }
+    forWritten(input) {
+        return this.build({
+            bucket: input.bucket,
+            eventName: input.eventName,
+            key: input.object.key,
+            caller: input.caller,
+            size: input.object.body.length,
+            eTag: input.object.etag,
+            versionId: input.versionId,
+        });
+    }
     build(raised) {
         const scope = raised.bucket.getAccountRegionScope();
         const bucketName = raised.bucket.bucketName;

package/dist/service/s3/notification/sim-s3-object-notifier.d.ts

@@ -1,6 +1,6 @@
 import type { BackgroundScheduler } from "../../../util/background/background.js";
 import type { SimS3NotificationDestinations } from "./destination/sim-s3-notification-destination.js";
-import { type SimS3ObjectCreatedInput, type SimS3ObjectRemovedInput } from "./event/sim-s3-object-event-builder.js";
+import { type SimS3ObjectCreatedInput, type SimS3ObjectRemovedInput, type SimS3ObjectTaggedInput } from "./event/sim-s3-object-event-builder.js";
 import type { SimS3NotificationDeliveryFailure } from "./sim-s3-notification-failures.js";
 interface SimS3ObjectNotifierProperties {
     readonly destinations: SimS3NotificationDestinations;
@@ -29,6 +29,10 @@ export declare class SimS3ObjectNotifier {
      * Raise an Object creation, as whichever kind of creation it was.
      */
     objectCreated(input: SimS3ObjectCreatedInput): void;
+    /**
+     * Raise a change to an Object's tags, as whichever kind of change it was.
+     */
+    objectTagged(input: SimS3ObjectTaggedInput): void;
     /**
      * Raise an Object removal, as whichever kind of removal it was.
      */

package/dist/service/s3/notification/sim-s3-object-notifier.js

@@ -36,6 +36,12 @@ export class SimS3ObjectNotifier {
     objectCreated(input) {
         this.schedule.matching(input.bucket, input.eventName, input.object.key, () => this.events.forCreated(input));
     }
+    /**
+     * Raise a change to an Object's tags, as whichever kind of change it was.
+     */
+    objectTagged(input) {
+        this.schedule.matching(input.bucket, input.eventName, input.object.key, () => this.events.forTagged(input));
+    }
     /**
      * Raise an Object removal, as whichever kind of removal it was.
      */

package/dist/service/s3/object/s3-key-encoding.d.ts

@@ -0,0 +1,12 @@
+/**
+ * An Object key in the encoded form S3 hands one back in.
+ *
+ * S3 form-URL-encodes a key, so a space becomes a plus sign, while the slashes
+ * that make up a key prefix stay as they are. An event notification record
+ * carries a key this way, and so does a listing that asked for one.
+ *
+ * The encoding is what lets a key hold a character XML cannot carry. An
+ * unencoded key holding a control character is a document no parser will read,
+ * which is the reason `EncodingType` exists.
+ */
+export declare function simS3EncodedKey(key: string): string;

package/dist/service/s3/object/s3-key-encoding.js

@@ -0,0 +1,14 @@
+/**
+ * An Object key in the encoded form S3 hands one back in.
+ *
+ * S3 form-URL-encodes a key, so a space becomes a plus sign, while the slashes
+ * that make up a key prefix stay as they are. An event notification record
+ * carries a key this way, and so does a listing that asked for one.
+ *
+ * The encoding is what lets a key hold a character XML cannot carry. An
+ * unencoded key holding a control character is a document no parser will read,
+ * which is the reason `EncodingType` exists.
+ */
+export function simS3EncodedKey(key) {
+    return encodeURIComponent(key).replaceAll("%20", "+").replaceAll("%2F", "/");
+}

package/dist/service/s3/object/s3-listing-encoding.d.ts

@@ -0,0 +1,42 @@
+import type { SimS3CommonPrefix } from "./s3-common-prefix.js";
+import type { SimS3ObjectSummary } from "./s3-object-summary.js";
+/**
+ * How a listing writes the keys it answers with.
+ *
+ * A listing hands back keys, the prefix and delimiter it was asked for, and the
+ * marker the next page starts at. All of them are keys or parts of one, so all
+ * of them are encoded together or none of them are. That is what this decides,
+ * once, for the whole page.
+ *
+ * A listing that asked for no encoding is answered with the keys as they are
+ * stored, which is what almost every caller wants and what every caller got
+ * before `EncodingType` was read at all.
+ *
+ * https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html
+ */
+export declare class SimS3ListingEncoding {
+    /**
+     * The encoding type to report back, which real S3 echoes only when the
+     * listing asked for one.
+     */
+    readonly encodingType: string | undefined;
+    /**
+     * A value real S3 does not have is refused rather than quietly treated as no
+     * encoding, since a caller misspelling it would otherwise decode keys that
+     * were never encoded.
+     */
+    constructor(encodingType?: string);
+    /**
+     * One key, prefix, delimiter or marker as the listing carries it.
+     */
+    value(value: string | undefined): string | undefined;
+    /**
+     * The Objects on a page, each under the key the listing carries.
+     */
+    summaries(summaries: SimS3ObjectSummary[] | undefined): SimS3ObjectSummary[] | undefined;
+    /**
+     * The folders a page rolled keys up into, each under the prefix the listing
+     * carries.
+     */
+    commonPrefixes(commonPrefixes: SimS3CommonPrefix[] | undefined): SimS3CommonPrefix[] | undefined;
+}

package/dist/service/s3/object/s3-listing-encoding.js

@@ -0,0 +1,75 @@
+import { SimS3InvalidArgument } from "../error/sim-s3.error.js";
+import { simS3EncodedKey } from "./s3-key-encoding.js";
+/**
+ * The only encoding a listing can ask for, which is the only one real S3 has.
+ */
+const urlEncodingType = "url";
+/**
+ * How a listing writes the keys it answers with.
+ *
+ * A listing hands back keys, the prefix and delimiter it was asked for, and the
+ * marker the next page starts at. All of them are keys or parts of one, so all
+ * of them are encoded together or none of them are. That is what this decides,
+ * once, for the whole page.
+ *
+ * A listing that asked for no encoding is answered with the keys as they are
+ * stored, which is what almost every caller wants and what every caller got
+ * before `EncodingType` was read at all.
+ *
+ * https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html
+ */
+export class SimS3ListingEncoding {
+    /**
+     * The encoding type to report back, which real S3 echoes only when the
+     * listing asked for one.
+     */
+    encodingType;
+    /**
+     * A value real S3 does not have is refused rather than quietly treated as no
+     * encoding, since a caller misspelling it would otherwise decode keys that
+     * were never encoded.
+     */
+    constructor(encodingType) {
+        if (encodingType !== undefined && encodingType !== urlEncodingType) {
+            throw new SimS3InvalidArgument(`Not an EncodingType real S3 has: ${encodingType}. ` +
+                `The only one is "${urlEncodingType}".`);
+        }
+        this.encodingType = encodingType;
+    }
+    /**
+     * One key, prefix, delimiter or marker as the listing carries it.
+     */
+    value(value) {
+        if (value === undefined || this.encodingType === undefined) {
+            return value;
+        }
+        return simS3EncodedKey(value);
+    }
+    /**
+     * The Objects on a page, each under the key the listing carries.
+     */
+    summaries(summaries) {
+        if (summaries === undefined || this.encodingType === undefined) {
+            return summaries;
+        }
+        return summaries.map((summary) => 
+        /* v8 ignore next -- a listed Object always has a key */
+        summary.Key === undefined
+            ? summary
+            : { ...summary, Key: simS3EncodedKey(summary.Key) });
+    }
+    /**
+     * The folders a page rolled keys up into, each under the prefix the listing
+     * carries.
+     */
+    commonPrefixes(commonPrefixes) {
+        if (commonPrefixes === undefined || this.encodingType === undefined) {
+            return commonPrefixes;
+        }
+        return commonPrefixes.map((commonPrefix) => 
+        /* v8 ignore next -- a rolled-up folder always has a prefix */
+        commonPrefix.Prefix === undefined
+            ? commonPrefix
+            : { Prefix: simS3EncodedKey(commonPrefix.Prefix) });
+    }
+}

package/dist/service/s3/object/s3-object-response-headers.d.ts

@@ -4,6 +4,16 @@
 export interface SimS3ObjectResponseDescription {
     /** The system metadata S3 was told when the Object was written. */
     readonly metadata?: Readonly<Record<string, string>> | undefined;
+    /**
+     * The metadata the caller attached to the Object, under the keys it used
+     * rather than the prefixed names the headers carry.
+     */
+    readonly userMetadata?: Readonly<Record<string, string>> | undefined;
+    /**
+     * The headers the read asked to be served in place of the Object's own,
+     * under the same names, from its `response-` parameters.
+     */
+    readonly overrides?: Readonly<Record<string, string>> | undefined;
     /** The length of the body being served, in bytes. */
     readonly bodyLength: number;
     /** The Object's ETag, quoted as an HTTP entity tag. */
@@ -15,6 +25,13 @@ export interface SimS3ObjectResponseDescription {
      * of them rather than all of them.
      */
     readonly contentRange?: string | undefined;
+    /**
+     * The storage class the Object is in, for one outside the default class.
+     * Real S3 leaves the header off a Standard Object.
+     */
+    readonly storageClass?: string | undefined;
+    /** The encryption S3 applied when it stored the Object. */
+    readonly serverSideEncryption?: string | undefined;
 }
 /**
  * The headers S3 sets on a read from what it was told when the Object was
@@ -26,6 +43,17 @@ export interface SimS3ObjectResponseDescription {
  * client can decode. `Cache-Control` matters for a different reason, being the
  * only one of these a caller can set per Object rather than per response.
  *
+ * `x-amz-storage-class` and `x-amz-server-side-encryption` say where and how
+ * S3 keeps the Object. The class is set for an Object outside the default one,
+ * as real S3 sets it, and the encryption is set for every Object S3 stored
+ * itself.
+ *
+ * User-defined metadata goes back out under the `x-amz-meta-` prefix S3 sends
+ * it with, one header per entry. The prefix is what keeps a caller's own key
+ * apart from a header S3 sets itself, so an Object holding a `content-type`
+ * key is served an `x-amz-meta-content-type` header alongside its own content
+ * type rather than in place of it.
+ *
  * `ETag` and `Last-Modified` are not metadata but facts about the stored bytes,
  * and are what makes a conditional request or a content-hash comparison
  * possible over HTTP. `Content-Range` is a fact about the response rather than
@@ -37,3 +65,15 @@ export interface SimS3ObjectResponseDescription {
  * https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html
  */
 export declare function simS3ObjectResponseHeaders(description: SimS3ObjectResponseDescription): Record<string, string>;
+/**
+ * The response headers a read asked to be served in place of the Object's own.
+ *
+ * Real S3 has one of these per system metadata header, named after it, so they
+ * are read by the same list rather than spelled out again. `Content-Type` and
+ * `Content-Disposition` are the two worth having: a presigned URL naming them
+ * decides whether the browser opens the file or saves it, and under what name,
+ * without anything being written to the Object.
+ *
+ * https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
+ */
+export declare function simS3ResponseHeaderOverrides(query: URLSearchParams): Record<string, string>;