[
https://issues.apache.org/jira/browse/KNOX-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2269:
--------------------------------
Description:
KNOX-2226 added the new Home Page to Knox which is bound to the default context
path in Jetty ({{/}}). However, this breaks the default topology feature: if a
default topology is declared (by setting {{default.app.topology.name}} in
{{gateway-site.xml}}) the homepage won't load.
Recommended solution:
# Add the Knox Home page like a regular Knox application rather than a generic
web app in the Knox Jetty server with web.xml, etc. This will allow it to be
deployed into topologies.
# Add a new topology (descriptor) called {{homepage}}. This will allow for a
gateway URL like
[https://gateway-host:8443/gateway/homepage|https://gateway-host:8443/gateway/home]
- for anyone already familiar with Knox this would be pretty intuitive.
# The {{default.app.topology.name}} should default to '{{homepage'}}. So that,
if no custom default topology declared, the home page will be accessible just
like today. If someone sets {{default.app.topology.name}} in
{{gateway-site.xml}}, the home page will be available under
{{PROTOCOL://KNOX_HOST/GATEWAY_PATH/homepage/home}}
Cc. [~lmccay], [~krisden], [[email protected]], [~smore]
was:
KNOX-2226 added the new Home Page to Knox which is bound to the default context
path in Jetty ({{/}}). However, this breaks the default topology feature: if a
default topology is declared (by setting {{default.app.topology.name}} in
{{gateway-site.xml}}) the homepage won't load.
Recommended solution:
# Add the Knox Home page like a regular Knox application rather than a generic
web app in the Knox Jetty server with web.xml, etc. This will allow it to be
deployed into topologies.
# Add a new topology (descriptor) called home.xml. This will allow for a
gateway URL like [https://gateway-host:8443/gateway/home] - for anyone already
familiar with Knox this would be pretty intuitive.
# The {{default.app.topology.name}} should default to '{{home'}}. So that, if
no custom default topology declared, the home page will be accessible just like
today. If someone sets {{default.app.topology.name}} in {{gateway-site.xml}},
the home page will be available under {{PROTOCOL://KNOX_HOST/GATEWAY_PATH/home}}
Cc. [~lmccay], [~krisden], [[email protected]], [~smore]
> Make homepage working with default topology
> -------------------------------------------
>
> Key: KNOX-2269
> URL: https://issues.apache.org/jira/browse/KNOX-2269
> Project: Apache Knox
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> KNOX-2226 added the new Home Page to Knox which is bound to the default
> context path in Jetty ({{/}}). However, this breaks the default topology
> feature: if a default topology is declared (by setting
> {{default.app.topology.name}} in {{gateway-site.xml}}) the homepage won't
> load.
> Recommended solution:
> # Add the Knox Home page like a regular Knox application rather than a
> generic web app in the Knox Jetty server with web.xml, etc. This will allow
> it to be deployed into topologies.
> # Add a new topology (descriptor) called {{homepage}}. This will allow for a
> gateway URL like
> [https://gateway-host:8443/gateway/homepage|https://gateway-host:8443/gateway/home]
> - for anyone already familiar with Knox this would be pretty intuitive.
> # The {{default.app.topology.name}} should default to '{{homepage'}}. So
> that, if no custom default topology declared, the home page will be
> accessible just like today. If someone sets {{default.app.topology.name}} in
> {{gateway-site.xml}}, the home page will be available under
> {{PROTOCOL://KNOX_HOST/GATEWAY_PATH/homepage/home}}
> Cc. [~lmccay], [~krisden], [[email protected]], [~smore]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
