This repository has been archived by the owner on Feb 28, 2022. It is now read-only.
HTML Pipeline: Turn meta http-equiv instructions into real HTTP headers #122
Assignees
Labels
Comments
trieloff
added a commit
that referenced
this issue
Apr 29, 2019
Merged
adobe-bot
pushed a commit
that referenced
this issue
May 8, 2019
# [1.11.0](v1.10.2...v1.11.0) (2019-05-08) ### Features * **html:** enable setting of HTTP headers through link and meta HTML tags ([32e4494](32e4494)), closes [#122](#122)
|
🎉 This issue has been resolved in version 1.11.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
koraa
pushed a commit
that referenced
this issue
May 10, 2019
koraa
pushed a commit
that referenced
this issue
May 10, 2019
# [1.11.0](v1.10.2...v1.11.0) (2019-05-08) ### Features * **html:** enable setting of HTTP headers through link and meta HTML tags ([32e4494](32e4494)), closes [#122](#122)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Setting HTTP response headers requires a
pre.jsright now. An easier way would be to simply set<meta http-equiv="X-My-Header" content="My-Value">in the template and have the pipeline turn the HTML tag into an HTTP header.With the
X-ESIheader we are already scanning HTML content to determine headers and this would make it more flexible and applicable for a wider range of use cases.The text was updated successfully, but these errors were encountered: