@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class CustomErrorResponse extends Object implements Serializable, Cloneable
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.
Constructor and Description |
---|
CustomErrorResponse() |
Modifier and Type | Method and Description |
---|---|
CustomErrorResponse |
clone() |
boolean |
equals(Object obj) |
Long |
getErrorCachingMinTTL()
The minimum amount of time, in seconds, that you want CloudFront to cache the HTTP status code specified in
ErrorCode . |
Integer |
getErrorCode()
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
|
String |
getResponseCode()
The HTTP status code that you want CloudFront to return to the viewer along with the custom error page.
|
String |
getResponsePagePath()
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 . |
int |
hashCode() |
void |
setErrorCachingMinTTL(Long errorCachingMinTTL)
The minimum amount of time, in seconds, that you want CloudFront to cache the HTTP status code specified in
ErrorCode . |
void |
setErrorCode(Integer errorCode)
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
|
void |
setResponseCode(String responseCode)
The HTTP status code that you want CloudFront to return to the viewer along with the custom error page.
|
void |
setResponsePagePath(String responsePagePath)
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 . |
String |
toString()
Returns a string representation of this object; useful for testing and debugging.
|
CustomErrorResponse |
withErrorCachingMinTTL(Long errorCachingMinTTL)
The minimum amount of time, in seconds, that you want CloudFront to cache the HTTP status code specified in
ErrorCode . |
CustomErrorResponse |
withErrorCode(Integer errorCode)
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
|
CustomErrorResponse |
withResponseCode(String responseCode)
The HTTP status code that you want CloudFront to return to the viewer along with the custom error page.
|
CustomErrorResponse |
withResponsePagePath(String responsePagePath)
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 . |
public void setErrorCode(Integer errorCode)
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
errorCode
- The HTTP status code for which you want to specify a custom error page and/or a caching duration.public Integer getErrorCode()
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
public CustomErrorResponse withErrorCode(Integer errorCode)
The HTTP status code for which you want to specify a custom error page and/or a caching duration.
errorCode
- The HTTP status code for which you want to specify a custom error page and/or a caching duration.public void setResponsePagePath(String responsePagePath)
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 the ID
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
. If you don't want to specify a value, include an empty element,
<ResponsePagePath>
, in the XML document.
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.
responsePagePath
- 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 the ID
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
. If you don't want to specify a value, include an empty element,
<ResponsePagePath>
, in the XML document.
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.
public String getResponsePagePath()
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 the ID
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
. If you don't want to specify a value, include an empty element,
<ResponsePagePath>
, in the XML document.
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.
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 the ID
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
. If you don't want to specify a value, include an empty element,
<ResponsePagePath>
, in the XML document.
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.
public CustomErrorResponse withResponsePagePath(String responsePagePath)
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 the ID
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
. If you don't want to specify a value, include an empty element,
<ResponsePagePath>
, in the XML document.
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.
responsePagePath
- 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 the ID
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
. If you don't want to specify a value, include an empty element,
<ResponsePagePath>
, in the XML document.
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.
public void setResponseCode(String responseCode)
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
or 500
as the ResponseCode
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
. If you don't want to specify a value, include an empty element,
<ResponseCode>
, in the XML document.
responseCode
- 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
or 500
as the ResponseCode
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
. If you don't want to specify a value, include an empty element,
<ResponseCode>
, in the XML document.
public String getResponseCode()
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
or 500
as the ResponseCode
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
. If you don't want to specify a value, include an empty element,
<ResponseCode>
, in the XML document.
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
or 500
as the ResponseCode
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
. If you don't want to specify a value, include an empty element,
<ResponseCode>
, in the XML document.
public CustomErrorResponse withResponseCode(String responseCode)
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
or 500
as the ResponseCode
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
. If you don't want to specify a value, include an empty element,
<ResponseCode>
, in the XML document.
responseCode
- 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
or 500
as the ResponseCode
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
. If you don't want to specify a value, include an empty element,
<ResponseCode>
, in the XML document.
public void setErrorCachingMinTTL(Long errorCachingMinTTL)
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.
If you don't want to specify a value, include an empty element, <ErrorCachingMinTTL>
, in the
XML document.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
errorCachingMinTTL
- 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.
If you don't want to specify a value, include an empty element, <ErrorCachingMinTTL>
,
in the XML document.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
public Long getErrorCachingMinTTL()
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.
If you don't want to specify a value, include an empty element, <ErrorCachingMinTTL>
, in the
XML document.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
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.
If you don't want to specify a value, include an empty element, <ErrorCachingMinTTL>
,
in the XML document.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
public CustomErrorResponse withErrorCachingMinTTL(Long errorCachingMinTTL)
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.
If you don't want to specify a value, include an empty element, <ErrorCachingMinTTL>
, in the
XML document.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
errorCachingMinTTL
- 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.
If you don't want to specify a value, include an empty element, <ErrorCachingMinTTL>
,
in the XML document.
For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide.
public String toString()
toString
in class Object
Object.toString()
public CustomErrorResponse clone()
Copyright © 2013 Amazon Web Services, Inc. All Rights Reserved.