[
https://issues.apache.org/jira/browse/NIFI-15173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-15173.
-------------------------------------
Fix Version/s: 2.7.0
Resolution: Fixed
> NiFi Registry UI should redirect to frontend nifi-registry path when base URL
> is accessed
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-15173
> URL: https://issues.apache.org/jira/browse/NIFI-15173
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Registry
> Reporter: Rahul Verma
> Priority: Major
> Fix For: 2.7.0
>
> Original Estimate: 1m
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When the URL for NiFi Registry is launched, it does _not_ automatically
> redirect to the {{/nifi-registry}} path. Users must manually append
> {{/nifi-registry}} to the URL in the browser to reach the UI. This is causing
> confusion, extra user queries, and document-searching by users.
> *Steps to reproduce*
> # Navigate to the base URL (e.g. {{{}https://my-server:port/{}}}).
> # The UI does _not_ redirect to {{{}https://my-server:port/nifi-registry{}}}.
> # The user must manually enter {{…/nifi-registry}} in the browser address
> bar to reach the Registry UI.
> *Expected behavior*
> The base URL should either:
> * Automatically redirect to {{/nifi-registry}}
> *Actual behavior*
> Users land on the base URL but do not see the Registry UI; they must know to
> append {{/nifi-registry}} explicitly.
> *Impact*
> * Increases user queries to support.
> * Increases onboarding/documentation overhead.
> * Slight risk of users not finding the Registry UI or thinking the service
> is down.
> *Workarounds*
> Manual append of {{/nifi-registry}} in browser URL.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
