[
https://issues.apache.org/jira/browse/FELIX-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rütter updated FELIX-6782:
-------------------------------
Description:
Allow configuring custom response headers to error pages served by Jetty, for
example, when a HTTP 400 is returned in case of an invalid path.
Those requests would never end up in the embedding application.
With this change, the embedding application can still configure some custom
headers to these error pages.
{code:java}
org.apache.felix.http.jetty.errorPageCustomHeaders=Strict-Transport-Security=max-age=31536000##X-Custom-Header=123{code}
was:
Allow configuring custom response headers to error pages served by Jetty, for
example, when a HTTP 400 is returned in case of an invalid path.
Those requests would never end up in the embedding application.
With this change, the embedding can still configure some custom headers to
these error pages.
{code:java}
org.apache.felix.http.jetty.errorPageCustomHeaders=Strict-Transport-Security=max-age=31536000##X-Custom-Header=123{code}
> Allow adding custom headers to Jetty error pages
> ------------------------------------------------
>
> Key: FELIX-6782
> URL: https://issues.apache.org/jira/browse/FELIX-6782
> Project: Felix
> Issue Type: New Feature
> Components: HTTP Service
> Reporter: Paul Rütter
> Assignee: Paul Rütter
> Priority: Major
>
> Allow configuring custom response headers to error pages served by Jetty, for
> example, when a HTTP 400 is returned in case of an invalid path.
> Those requests would never end up in the embedding application.
> With this change, the embedding application can still configure some custom
> headers to these error pages.
> {code:java}
> org.apache.felix.http.jetty.errorPageCustomHeaders=Strict-Transport-Security=max-age=31536000##X-Custom-Header=123{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
