Struct aws_sdk_cloudfront::model::CustomErrorResponse [−][src]
#[non_exhaustive]pub struct CustomErrorResponse {
pub error_code: Option<i32>,
pub response_page_path: Option<String>,
pub response_code: Option<String>,
pub error_caching_min_ttl: Option<i64>,
}
Expand description
A complex type that controls:
-
Whether CloudFront replaces HTTP status codes in the 4xx and 5xx range with custom error messages before returning the response to the viewer.
-
How long CloudFront caches HTTP status codes in the 4xx and 5xx range.
For more information about custom error pages, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
Fields (Non-exhaustive)
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.error_code: Option<i32>
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
response_page_path: Option<String>
The path to the custom error page that you want CloudFront to return to a viewer when your
origin returns the HTTP status code specified by ErrorCode
, for example,
/4xx-errors/403-forbidden.html
. If you want to store your objects and your
custom error pages in different locations, your distribution must include a cache behavior for
which the following is true:
-
The value of
PathPattern
matches the path to your custom error messages. For example, suppose you saved custom error pages for 4xx errors in an Amazon S3 bucket in a directory named/4xx-errors
. Your distribution must include a cache behavior for which the path pattern routes requests for your custom error pages to that location, for example,/4xx-errors/*
. -
The value of
TargetOriginId
specifies the value of theID
element for the origin that contains your custom error pages.
If you specify a value for ResponsePagePath
, you must also specify a value
for ResponseCode
.
We recommend that you store custom error pages in an Amazon S3 bucket. If you store custom error pages on an HTTP server and the server starts to return 5xx errors, CloudFront can't get the files that you want to return to viewers because the origin server is unavailable.
response_code: Option<String>
The HTTP status code that you want CloudFront to return to the viewer along with the custom error page. There are a variety of reasons that you might want CloudFront to return a status code different from the status code that your origin returned to CloudFront, for example:
-
Some Internet devices (some firewalls and corporate proxies, for example) intercept HTTP 4xx and 5xx and prevent the response from being returned to the viewer. If you substitute
200
, the response typically won't be intercepted. -
If you don't care about distinguishing among different client errors or server errors, you can specify
400
or500
as theResponseCode
for all 4xx or 5xx errors. -
You might want to return a
200
status code (OK) and static website so your customers don't know that your website is down.
If you specify a value for ResponseCode
, you must also specify a value for
ResponsePagePath
.
error_caching_min_ttl: Option<i64>
The minimum amount of time, in seconds, that you want CloudFront to cache the HTTP status
code specified in ErrorCode
. When this time period has elapsed, CloudFront queries your
origin to see whether the problem that caused the error has been resolved and the requested
object is now available.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
Implementations
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
The path to the custom error page that you want CloudFront to return to a viewer when your
origin returns the HTTP status code specified by ErrorCode
, for example,
/4xx-errors/403-forbidden.html
. If you want to store your objects and your
custom error pages in different locations, your distribution must include a cache behavior for
which the following is true:
-
The value of
PathPattern
matches the path to your custom error messages. For example, suppose you saved custom error pages for 4xx errors in an Amazon S3 bucket in a directory named/4xx-errors
. Your distribution must include a cache behavior for which the path pattern routes requests for your custom error pages to that location, for example,/4xx-errors/*
. -
The value of
TargetOriginId
specifies the value of theID
element for the origin that contains your custom error pages.
If you specify a value for ResponsePagePath
, you must also specify a value
for ResponseCode
.
We recommend that you store custom error pages in an Amazon S3 bucket. If you store custom error pages on an HTTP server and the server starts to return 5xx errors, CloudFront can't get the files that you want to return to viewers because the origin server is unavailable.
The HTTP status code that you want CloudFront to return to the viewer along with the custom error page. There are a variety of reasons that you might want CloudFront to return a status code different from the status code that your origin returned to CloudFront, for example:
-
Some Internet devices (some firewalls and corporate proxies, for example) intercept HTTP 4xx and 5xx and prevent the response from being returned to the viewer. If you substitute
200
, the response typically won't be intercepted. -
If you don't care about distinguishing among different client errors or server errors, you can specify
400
or500
as theResponseCode
for all 4xx or 5xx errors. -
You might want to return a
200
status code (OK) and static website so your customers don't know that your website is down.
If you specify a value for ResponseCode
, you must also specify a value for
ResponsePagePath
.
The minimum amount of time, in seconds, that you want CloudFront to cache the HTTP status
code specified in ErrorCode
. When this time period has elapsed, CloudFront queries your
origin to see whether the problem that caused the error has been resolved and the requested
object is now available.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
Creates a new builder-style object to manufacture CustomErrorResponse
Trait Implementations
This method tests for self
and other
values to be equal, and is used
by ==
. Read more
This method tests for !=
.
Auto Trait Implementations
impl RefUnwindSafe for CustomErrorResponse
impl Send for CustomErrorResponse
impl Sync for CustomErrorResponse
impl Unpin for CustomErrorResponse
impl UnwindSafe for CustomErrorResponse
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more