[
https://issues.apache.org/jira/browse/TS-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641971#comment-14641971
]
Leif Hedstrom commented on TS-3779:
-----------------------------------
[~jacksontj] I was thinking about that too, but it'd be much more difficult to
implement. Today, we parse / load these templates at startup, but if it's
overridable, you could theoretically load / parse them on a request. The code
likely was not intended for that, i.e. it's possibly both slow and wasteful :).
It can obviously store / cache these templates once loaded, but we would have
to rethink how we do these page honestly.
Also, I really feel we should redo body factory completely at some point, maybe
for 7.0.0. It's very inefficient already, and not particularly flexible. And
I'd really like to see it usable from plugin APIs, not just as you suggested,
but also as a generic "template" expander (it could replace the expander in
e.g. header rewrite and such plugins / tools).
> Body Factory: support per hosts error pages.
> --------------------------------------------
>
> Key: TS-3779
> URL: https://issues.apache.org/jira/browse/TS-3779
> Project: Traffic Server
> Issue Type: New Feature
> Components: Core
> Reporter: Brian Geffon
> Assignee: Brian Geffon
> Labels: review
> Fix For: 6.0.0
>
>
> Body Factory should support per-host error pages as it supports per-language
> error pages today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)