[
https://issues.apache.org/jira/browse/TS-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680672#comment-14680672
]
ASF subversion and git services commented on TS-3831:
-----------------------------------------------------
Commit e985569ae95fa6345f6302d1340d4e9b4e64b804 in trafficserver's branch
refs/heads/master from [~persiaAziz]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e985569 ]
TS-3831: overridable error response type
This closes #273.
> Overridable error response type
> -------------------------------
>
> Key: TS-3831
> URL: https://issues.apache.org/jira/browse/TS-3831
> Project: Traffic Server
> Issue Type: New Feature
> Components: Configuration
> Reporter: Syeda Persia Aziz
>
> ATS has a set of error pages in the folder body_factory, namely
> access#denied, access#proxy_auth_required,connect#dns_failed... etc. All
> these error pages are loaded in a RawHashTable. When there is an error for
> e.g. access denied, ATS builds a error response of type access#denied. We
> can have an overridable config that will decide which custom error page to
> send to the client. This config will be set per remap rule. We can have the
> custom error pages in the body_factory folder and these pages will follow a
> specific naming convention for e.g. $var_access#denied,
> $var_access#proxy_auth_required, ….. Here $var is the overridable config
> (proxy.config.error.response.type).
> Example:
> in Remap.config
> map www.abcxyz.com www.efgijk.com @plugin=config.so
> @pparam=proxy.config.error.response.type=yahoo
> Now, if there is for e.g. a 'access denied' error, the build_error_response
> will build a customized error response of type yahoo_access#denied . If it
> can not find the type yahoo_access#denied, then it will simply build the
> default access#denied error response.
> Note: I already have a patch for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
