Executed for rendering a file within a HTML document. Also called, inlining the file.
When a file implements the
.Inline interface by having an
.Inline file on
its type chain, the file is said to be a content.
headdefined on the response file. Tags defined in this attribute are expected to be propagated by the callee. Note that the
<title>tag is not allowed, setting it is the concern of the top-most transaction (responding to a request as defined in
0which has the same meaning as
200. Any non
200status-code is expected to be propagated by the callee and returned to the client. 3xx beats anything under 300, 4xx beats 3xx, 5xx beats 4xx. The first from any status-code category (200, 3xx, 4xx, 5xx) will be returned.
content-security-policyof the response file. If a
.ContentSecurityPolicyfile is defined on the app, Boomla will pick it up the rules automatically, before the .Inline method is executed.
Note that the
.Inline file is executed transactionally in an isolated
environment. Upon a server error or a 5xx statusCode, the entire transaction
will be rolled back. (If you removed files, those changes will not take effect.)
This saves you from implementing a rollback logic yourself.