@aws-sdk/middleware-sdk-s3/dist-types/submodules/s3/protocol/S3RestXmlProtocol.d.ts

[](https://www.npmjs.com/package/@aws-sdk/middleware-sdk-s3) [](https://www.npmjs.com/package/@

import { AwsRestXmlProtocol } from "@aws-sdk/core/protocols";
import type { EndpointBearer, HandlerExecutionContext, HttpRequest, OperationSchema, SerdeFunctions } from "@smithy/types";
/**
 * Customization for S3 backwards compatibility.
 *
 * In the S3 model, Bucket is considered an HTTP label, and we normally perform http label client
 * side validation. However, the standard validation is that the http label appears in
 * the request path. Bucket is unique in that it is an endpoint context param. It appears
 * where the endpoint resolver decides, rather than in the URL path (although sometimes it does appear there).
 *
 * For consistency with older code generated clients, we throw the HTTP label validation
 * error when the Bucket input is missing, if-and-only-if it is an httpLabel and is a required top level member.
 *
 * This does not apply to S3 Control.
 *
 * @internal
 */
export declare class S3RestXmlProtocol extends AwsRestXmlProtocol {
    serializeRequest<Input extends object>(operationSchema: OperationSchema, input: Input, context: HandlerExecutionContext & SerdeFunctions & EndpointBearer): Promise<HttpRequest>;
}