/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include The cross-origin
* resource sharing (CORS) settings for your Lambda function URL. Use CORS to
* grant access to your function URL from any origin. You can also use CORS to
* control access for specific HTTP headers and methods in requests to your
* function URL.See Also:
AWS API
* Reference
Whether to allow cookies or other credentials in requests to your function
* URL. The default is false
.
Whether to allow cookies or other credentials in requests to your function
* URL. The default is false
.
Whether to allow cookies or other credentials in requests to your function
* URL. The default is false
.
Whether to allow cookies or other credentials in requests to your function
* URL. The default is false
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP headers that origins can include in requests to your function URL.
* For example: Date
, Keep-Alive
,
* X-Custom-Header
.
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The HTTP methods that are allowed when calling your function URL. For
* example: GET
, POST
, DELETE
, or the
* wildcard character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The origins that can access your function URL. You can list any number of
* specific origins, separated by a comma. For example:
* https://www.example.com
, http://localhost:60905
.
Alternatively, you can grant access to all origins using the wildcard
* character (*
).
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The HTTP headers in your function response that you want to expose to origins
* that call your function URL. For example: Date
,
* Keep-Alive
, X-Custom-Header
.
The maximum amount of time, in seconds, that web browsers can cache results
* of a preflight request. By default, this is set to 0
, which means
* that the browser doesn't cache results.
The maximum amount of time, in seconds, that web browsers can cache results
* of a preflight request. By default, this is set to 0
, which means
* that the browser doesn't cache results.
The maximum amount of time, in seconds, that web browsers can cache results
* of a preflight request. By default, this is set to 0
, which means
* that the browser doesn't cache results.
The maximum amount of time, in seconds, that web browsers can cache results
* of a preflight request. By default, this is set to 0
, which means
* that the browser doesn't cache results.