Sandeep More created KNOX-1858:
----------------------------------
Summary: For a configured list of services fix X-Forwarded-Context
header to add service name
Key: KNOX-1858
URL: https://issues.apache.org/jira/browse/KNOX-1858
Project: Apache Knox
Issue Type: Bug
Components: Server
Reporter: Sandeep More
Assignee: Sandeep More
Fix For: 1.3.0
*X-Forward-Context* header for Knox does not behave as it should, it should be
*/\{gateway}/\{topology}/\{serviceName}* but currently it is
*/\{gateway}/\{topology}.*
This will create issues where the proxied applications have no way of knowing
the true context (they should not care and mostly they do not, but there are
exceptions).
The problem in fixing this the right way is that we might end up breaking
existing applications they rely on this behavior.
It has been suggested we introduce a config property
(gateway.header.x-forward-context.append.servicename) in gateway-site.xml that
will take a list of service names and if the property is defined and list not
empty for those services Knox will correct the *X-Forward-Context* header.
Proposed config snippet in gateway-site.xml
{code:java}
<property>
<name>gateway.header.x-forward-context.append.servicename</name>
<value>livy, sparkhistory</value>
</property>
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
