Skip to content

NIFI-14165 Fix Context Path Support for Default Server Handler#9653

Closed
exceptionfactory wants to merge 1 commit intoapache:mainfrom
exceptionfactory:NIFI-14165
Closed

NIFI-14165 Fix Context Path Support for Default Server Handler#9653
exceptionfactory wants to merge 1 commit intoapache:mainfrom
exceptionfactory:NIFI-14165

Conversation

@exceptionfactory
Copy link
Contributor

Summary

NIFI-14165 Corrects application server handling of unknown HTTP requests when NiFi is configured to run behind a proxy server with an alternate context path.

The updated implementation passes the list of allowed context paths configured from nifi.web.proxy.context.path in nifi.properties to a new Jetty redirect rule implementation. When the HTTP request includes a proxy context path header with a value from the allowed list of paths, the redirect rule prefixes the location with the context path. This correction ensures that requests for invalid or unknown URLs will be redirected to the standard user interface path when NiFi is running behind a proxy server.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using mvn clean install -P contrib-check
    • JDK 21

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

- Added Context Path Redirect Pattern Rule support allowed context paths when redirecting requests for unknown paths
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants